From: Vladimir Vorobyov <vladimir.vorobyov@iss.org.ua>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: pthreads debug with gdbserver
Date: Sat, 20 Nov 2004 16:42:00 -0000 [thread overview]
Message-ID: <200411201427.13557.vladimir.vorobyov@iss.org.ua> (raw)
In-Reply-To: <20041120013220.GB27485@nevyn.them.org>
Thank for your inputs. I moved further - see below.
> > info shared reports: "No shared libraries loaded at this time".
> > Straces shows that gdb opens only ld.so file.
> > When adding printf to solibopen it also shows only ld.so.
> > Who is responsible for loading shared libs ? What file/function/event?
>
> This usually means that the ld.so GDB has opened is not -exactly- the
> same as the one on your target; and then it has set the solib event
> breakpoint at the wrong location, and it hasn't been hit. Take a look
> at solib-svr4.c if you want more details.
As I said in my first message the breakpoint is hit exactly 3 times. I found
that current_sos in solib-svr4.c can not find any libraries. It was because
first_link_map_member returned NULL. After this I found that
SVR4_FETCH_LINK_MAP_OFFSETS did not return correct offsets (which are correct
for me? ilp32?). I tried to follow those gdbach_data calls but it was too
difficult. I just assigned svr4_ilp32_fetch_link_map_offsets to
SVR4_FETCH_LINK_MAP_OFFSETS (how to do it correctly?).
After this with every shlib breakpoint hit gdb loads appropriate shared lib
BUT gdbserver reports "Target does not support breakpoints" 3 times for each
library loaded. What does it mean ?
I still receive SIG32, info threads still shows only one thread. "info shared"
shows all libraries that are loaded and td_ta_new() call now returns
successfully.
> > Yes, the problem number one is that GDB does not auto loads shared libs.
> > Is it not the same when I manually add-symbol-file lipthread.so? Can I do
> > it to load shared libs ?
> > When I do this I got "gbd: error initializing thread_db library." error
> > on the target. When I add debug info to it, I see that error is
> > "Incompatible versions of libpthread and libthread_db". But these two
> > libs are from the same libc.
> > It looks like this is my second problem. Or it depends on first one and
> > may disappear when first problem is solved?
>
> Are you sure you loaded the right copy?
Absolutely.
Regards,
Vladimir.
next prev parent reply other threads:[~2004-11-20 12:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 14:23 Vladimir Vorobyov
2004-11-19 14:42 ` Daniel Jacobowitz
2004-11-19 15:59 ` Vladimir Vorobyov
2004-11-20 10:01 ` Daniel Jacobowitz
2004-11-20 16:42 ` Vladimir Vorobyov [this message]
2004-11-20 16:57 ` Daniel Jacobowitz
2004-11-20 17:13 ` Andreas Schwab
2004-11-20 17:38 ` Vladimir Vorobyov
2004-12-06 18:41 ` NPTL on ppc (was: pthreads debug with gdbserver) Linh Dang
2004-12-06 18:45 ` Daniel Jacobowitz
2004-12-06 19:56 ` NPTL on ppc Linh Dang
2004-12-06 20:18 ` Daniel Jacobowitz
2004-12-06 22:41 ` Andreas Schwab
2004-12-06 23:20 ` Andreas Schwab
2004-12-07 14:33 ` Linh Dang
2004-12-07 14:56 ` Andreas Schwab
2004-12-06 22:04 ` Andreas Schwab
2004-11-22 14:07 ` pthreads debug with gdbserver Vladimir Vorobyov
2004-11-22 18:04 ` Daniel Jacobowitz
2004-11-23 19:33 ` Vladimir Vorobyov
2004-11-19 16:19 ` Andreas Schwab
2004-11-19 17:30 ` Vladimir Vorobyov
2004-11-20 1:31 ` Andreas Schwab
2004-11-20 1:32 ` 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=200411201427.13557.vladimir.vorobyov@iss.org.ua \
--to=vladimir.vorobyov@iss.org.ua \
--cc=drow@false.org \
--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