lldb developers, I am having a problem with lldb that I hope you can help with.
I am debugging some C++ by running it, and attaching to the process with lldb.
I get a nonsensical backtrace like this:
thread #37, name = 'xmsim', stop reason = signal SIGSTOP
frame #0: 0x2b96a2ab1409
thre
Hi Pavel, Eugene, here is a testcase that demonstrates the problem. The code
that sets up sigalrm in main() is the same as the program I have been debugging
except that I’ve reduced the interval in this testcase. In the original, as
per the comment, the interval is .8 seconds.
When I run this
Ding! That’s it. This program does use SIGALRM. I wouldn’t have thought it
would be enabled at this point, but apparently it is because I got lots of
sigalarm halts during the .so loading.
Further, if I run in lldb with
process handle -n false -p false -s false SIGALRM
then the debugger se
Pavel asked for a dump of gdb-remote commands. I got that and ran it through the gdbremote decoder, and trimmed to include what looks like the last successful continue after breakpoint and then the halt on dlopen. Both cases stop on signal 5.After the stop message the debugger issues two binary r
