From: Matteo Fortini <m.fortini@selcomgroup•com>
To: linuxppc-embedded@ozlabs•org
Subject: Re: gdbserver not working with pthreads
Date: Fri, 19 Sep 2008 14:26:39 +0200 [thread overview]
Message-ID: <48D39A7F.9090301@selcomgroup.com> (raw)
In-Reply-To: <48D20FCC.6070602@selcomgroup.com>
I answer to myself: the cvs version of gdbserver works properly, so I
guess the issue was solved very recently.
M
Matteo Fortini ha scritto:
> I'm using gdbserver & gdb-cross built on OpenEmbedded, both versions
> 6.6 and 6.8 on FSL kernel 2.6.24.6 with an MPC5121 cpu, glibc 2.6.1
>
> Gdb on the target is working properly, and can debug threads the usual
> way.
>
> When debugging with gdbserver/gdb the debugger loses control of the
> threads. I did set the sysroot variable right, and I don't get the ld
> not found error message.
> Basically, I cannot step into pthread_create, without losing control,
> with the software not running and gdb going timeout. Sometimes the
> gdbserver shell prints out "ptrace(): pid not found", or I get E01
> reply on the gdb-cross. Putting breakpoints into threads works sometimes.
> My ultimate goal would be to make it work with Eclipse, but it's a
> long way from having it working with such a system.
>
> I attach the simple software I'm using to test it.
>
> I also tried setting the target architecture to values other than
> powerpc:common, but it didn't help.
>
> Thank you for any clue,
> Matteo
> ------------------------------------------------------------------------
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
next prev parent reply other threads:[~2008-09-19 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 8:22 gdbserver not working with pthreads Matteo Fortini
2008-09-19 12:26 ` Matteo Fortini [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-18 16:37 Sugathan, Rupesh
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=48D39A7F.9090301@selcomgroup.com \
--to=m.fortini@selcomgroup$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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