Odd signal behavior when starting certain command line applications via Debugger
|Reported by:||anevilyak||Owned by:||anevilyak|
|Has a Patch:||no||Platform:||All|
If one runs e.g.
/system/apps/Debugger /bin/info from Terminal, waits for the debugger window to come up, then closes it and chooses to resume the app at the prompt, the app subsequently crashes due to a stack overflow. From the corresponding backtrace, it's not entirely clear what's going on though, the app seems to keep getting handed a SIGTTIN while it's in the process of handling the previous one. This behavior only seems to be observable with apps that do something curses-based though.
The only obvious difference that comes to mind is that Debugger spawns the requested app via load_image(), while in normal circumstances they're run via fork/exec from bash. In any case, the corresponding crash report for info is attached (in compressed form, since it winds up being 25MB due to the size of the backtrace). I've assigned it to System due to not being certain as to the actual culprit here.