Feel free to file a bug on the Linux support in lldb to read out this value. Darwin doesn't support this part of the real time signals spec, so we didn't have signals with values originally, but there's no reason not to support it on systems that have signal values.
Jim > On Jun 1, 2015, at 5:43 PM, Eugene Birukov <[email protected]> wrote: > > Hi, > > I need the deguggee to stop and pass some information to the debugger - if > the debugger is attached, that is. And I want to do it from different threads > in concurrent manner. So, I thought maybe I use run-time signals on Linux: > i.e. the thread would: > • Fill out some buffer with data the debugger needs to see > • Send signal 35 to itself passing the address of the buffer as a > payload: > > • sigval value; > • value.sival_ptr = address; > • sigqueue(gettid(), 35, value); > > • In the signal handler just ignore the signal > > If debugger is attached, it will see the signal and inspect > info->si_value.sival_ptr. But unfortunately LLDB reports only signal number > and drops the value on the floor. > > So, is there any other "legal" way to achieve what I need? > > Thanks, > Eugene > _______________________________________________ > lldb-dev mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
