From: Daniel Jacobowitz <drow@false.org>
To: "Steven J. Hill" <sjhill@realitydiluted.com>
Cc: "FALE(Leopold Faschalek)" <FALE@skidata.com>, gdb@sourceware.org
Subject: Re: Linux threads and insight 6.4 / 6.5
Date: Thu, 29 Jun 2006 15:14:00 -0000 [thread overview]
Message-ID: <20060628023440.GA29935@nevyn.them.org> (raw)
In-Reply-To: <44A1CCC5.1090606@realitydiluted.com>
On Tue, Jun 27, 2006 at 07:26:45PM -0500, Steven J. Hill wrote:
> FALE(Leopold Faschalek) wrote:
> >
> > The thread model is linuxthreads (not NPTL).
> >
> > ================== target ======================
> > /img # ./gdbserver64 192.168.184.10:5000 ./test
> > Process ./test created; pid = 370
> > Listening on port 5000
> > Remote debugging from host 192.168.184.10
> >
> > Child terminated with signal = 9
> >
> > Child terminated with signal = 0x9
> > GDBserver exiting
Sorry, I didn't respond to this because I don't know what could cause
it. You might want to search the archives for problems with thread
debugging; the usual suspects are library mismatches.
> That's okay. I'm using NPTL on MIPS with the latest gdbserver (6.5) and
> it does the exact same thing for me, kind of. Mine exits with signal 5.
> As usual, threads support is iffy.
With signal 5 is a clear signal that gdbserver has not enabled thread
support, either because of a mismatch or a problem with libthread_db
support on your target. When one thread hits a breakpoint, if another
thread is running outside of debugger control, the kernel may terminate
the entire process.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-28 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 7:10 FALE(Leopold Faschalek)
2006-06-29 11:53 ` Steven J. Hill
2006-06-29 15:14 ` Daniel Jacobowitz [this message]
2006-06-30 0:11 ` Steven J. Hill
2006-06-30 17:27 ` 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=20060628023440.GA29935@nevyn.them.org \
--to=drow@false.org \
--cc=FALE@skidata.com \
--cc=gdb@sourceware.org \
--cc=sjhill@realitydiluted.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