Opened 13 years ago
Closed 12 years ago
#7988 closed bug (fixed)
[Debugger] odd Terminal launch
| Reported by: | diver | Owned by: | phoudoin |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications/Debugger | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
This is hrev42754, gcc4hybrid.
Looking at Teams window of the Debugger app and launching Terminal shows somewhat odd behavior:
- /bin/bash appears and disappears several times under different IDs.
- There are two Terminal entries in the Teams window with different IDs.
- There is no /bin/bash in that list until Debugger restart.
- Sometimes Terminal's icon appears as generic app icon.
Attachments (2)
Change History (11)
by , 13 years ago
| Attachment: | Debugger.ogv added |
|---|
comment:1 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 13 years ago
comment:3 by , 13 years ago
I guess indeed that the current code don't handle fine the fork/exec case:
- Two Terminals teams is due to the fork
- after the exec, the Terminal team is still there, but now running the shell: it's not detect by the code, as the team ID was already seen at previous update cycle.
- The Terminal icon appearing as a generic app icon must be due that while the code don't detect that the team is not anymore running the same executable, the icon is retrieved *after* the team's command line has change, leading to... /bin/bash generic app icon.
So, I guess I should redesign it a bit in order to handle the fork/exec case, indeed. I fear Process Controller teams menu could suffer the same issue here, BTW.
Version 0, edited 13 years ago by (next)
comment:5 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:6 by , 13 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
by , 12 years ago
| Attachment: | Debugger_hrev44361.ogv added |
|---|
comment:8 by , 12 years ago
Apart from the second Terminal with id 1041 and the fact that it takes 4-5 seconds for Terminal to start in vbox everything is fine now.
comment:9 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Thanks you for (video!) report.
Note:
See TracTickets
for help on using tickets.
Some of parts 1 and 2 isn't a complete surprise because of the fork/execs that go on in the process of spawning the child bash (which itself does some more of this in order to run the env setup scripts, etc.). Probably an exec gets missed somewhere resulting in the team not properly getting updated to reflect its new running executable image. Phiippe has done more with the teams window though, so he might have better insight.