From: "Michael Zhang" <michael.gd.zhang@gmail.com>
To: "Michael Snyder" <Michael.Snyder@access-company.com>
Cc: gdb@sourceware.org
Subject: Re: remotely debugging muti-threaded applicaton did not work with gdb 6.3.50.20050725-cvs
Date: Tue, 29 May 2007 19:27:00 -0000 [thread overview]
Message-ID: <3d234af30705291227m584060a1jd1007594719bfd47@mail.gmail.com> (raw)
In-Reply-To: <655C3D4066B7954481633935A40BB36F041337@ussunex02.svl.access-company.com>
Thanks all,
I will try 6.6 and keep you posted.
Cheers,
Michael
On 5/29/07, Michael Snyder <Michael.Snyder@access-company.com> wrote:
>
>
>
> Most likely your target is configured to use the new NPTL threads.
> GDB 6.3 is quite good at handling NPTL threads, but unfortunately,
> gdbserver 6.3 isn't.
>
> If you can upgrade to GDB 6.6, that would be best.
>
> At a minimum, you need to build the gdbserver from version 6.6
> and install it on your target.
>
> Michael
>
>
>
> -----Original Message-----
> From: gdb-owner@sourceware.org on behalf of Michael Zhang
> Sent: Tue 5/29/2007 9:13 AM
> To: gdb@sourceware.org
> Subject: remotely debugging muti-threaded applicaton did not work with gdb
> 6.3.50.20050725-cvs
>
> Hi there,
>
> I have been battling with this problem for a week now and searched
> all the available information ( GDB manual, gdb mailing list, etc.)
> but unfortunately could not find an answer. Here is my setup.
>
> - Host : x86 running FC1 with linux 2.4.22-1.2115.nptl
> - Target : mips le running linux 2.4.17
> - gdb 6.3.50.20050725-cvs and its included gdbserver (all cross-built
> for mips processor)
> - libc library 2.2.3 ( most of the shared library bear this version )
>
> Debugging problem:
>
> The gdb on the host can talk to the gdbserver on the target and I did
> not forget to set "solib-absolute-prefix". If I set breakpoints before
> the multiple threads are spawned, I could step through the code when
> the breakpoint was hit. However, once the application finished
> creating threads and if I stop the program to step through, it won't
> step and alway stuck in libc.so.6. The worst is all the threads are
> getting killed. And "info threads" never returns anything just
> reporting that the gdbserver could not get thread list.
>
> Any ideas even though it might have bee asked before. I am basically
> at my wit's end.
>
> Cheers,
>
> Michael
>
>
next prev parent reply other threads:[~2007-05-29 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 16:14 Michael Zhang
2007-05-29 16:22 ` David Daney
[not found] ` <655C3D4066B7954481633935A40BB36F041337@ussunex02.svl.access-company.com>
2007-05-29 19:27 ` Michael Zhang [this message]
2007-05-31 17:23 ` 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=3d234af30705291227m584060a1jd1007594719bfd47@mail.gmail.com \
--to=michael.gd.zhang@gmail.com \
--cc=Michael.Snyder@access-company.com \
--cc=gdb@sourceware.org \
/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