This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Fri, 2002-12-06 at 16:17, Daniel Jacobowitz wrote: > Thread events aren't reported immediately for latency reasons; but they > should all be delivered the first time the child stops... > Even after the threads are all finished, I don't see anything stepping into handle_inferior_event() other then when the initial manager thread is created. > > Also, on the gdb side of things, it doesn't look like there are any > > events happening .. thus handle_inferior_event() is never stepped into > > at thread creation/running/exit time. Although td_thr_event_enable() > > still returns TD_OK. > > Wait, what's going on? Are you saying td_thr_event_enable is being > called on your host GDB? That's not going to work right. > I meant handle_inferior_event() on host gdb and td_thr_event_enable() being invoked from maybe_attach_thread() on the gdbserver side. > > Notably, if I connect gdb to gdbserver while gdb and gdbserver are both > > running under gdb control, SIG32 issues appear again.. > > gdbserver may get a SIG32 while debugging; set the process debugging > gdbserver to "nostop noprint pass" that signal. Ditto SIG33, I think. Doing that already as a workaround, wasn't positive if this was expected or not. Regards, -- Paul Mundt <paul.mundt@timesys.com> TimeSys Corporation
Attachment:
signature.asc
Description: This is a digitally signed message part
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |