From: Paul Mundt <paul.mundt@timesys.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: Gdbserver Threading Issues
Date: Fri, 06 Dec 2002 13:07:00 -0000 [thread overview]
Message-ID: <1039212714.11722.98.camel@Origin> (raw)
In-Reply-To: <20021206192849.GA4411@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
On Fri, 2002-12-06 at 14:28, Daniel Jacobowitz wrote:
> Not without more information. Look at the remote session transcript,
> see what is going on.
Hum, still debugging this .. I'm still at a loss as to why breakpoints
would be having any effect on anything, though from the looks of it the
newly created threads are tracked just fine by
thread_db_find_new_threads() in gdbserver/thread-db.c
Also single stepping through maybe_attach_thread() everything looks
alright, though still the threads don't show up on the GDB side.
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.
I'm still a bit unsure as to the code flow for most of this, so I
suppose more debugging is in order..
Notably, if I connect gdb to gdbserver while gdb and gdbserver are both
running under gdb control, SIG32 issues appear again..
Regards,
--
Paul Mundt <paul.mundt@timesys.com>
TimeSys Corporation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-12-06 21:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 11:20 Paul Mundt
2002-12-06 11:28 ` Daniel Jacobowitz
2002-12-06 13:07 ` Paul Mundt [this message]
2002-12-06 13:16 ` Daniel Jacobowitz
2002-12-06 13:20 ` Paul Mundt
2002-12-06 13:23 ` Daniel Jacobowitz
2002-12-06 13:33 ` Paul Mundt
2002-12-06 13:35 ` Daniel Jacobowitz
2002-12-06 13:59 ` Paul Mundt
2002-12-06 14:08 ` Daniel Jacobowitz
2002-12-06 14:15 ` Paul Mundt
2002-12-06 17:15 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1039212714.11722.98.camel@Origin \
--to=paul.mundt@timesys.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox