Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: gdb@sources.redhat.com
Subject: multithreaded gdbserver again.  Should I use gdb5.3, or a snapshot?
Date: Tue, 08 Apr 2003 06:05:00 -0000	[thread overview]
Message-ID: <3E926917.1050900@kegel.com> (raw)

Hi all,
I had the multithreaded gdbserver from gdb-5.3 working, but
never tried really debugging anything with it.  I recently
brought it back up, and tried it out a bit.  I ran into the usual
set of newbie problems, namely:

* I didn't have solib-absolute-prefix set properly;
   this was made clear with the commands
     break main
     cont
     info shared
   which showed the wrong path.  I gave the command
     set solib-absolute-prefix /opt/cegl-1.5/hardhat/devkit/sh/sh4_le/target
   and that helped gdb find the shared libraries

* The libthread_db.so on the target was stripped, which seems to have
   caused SIG32 messages.  I made sure both gdb and gdbserver had
   the same unstripped libthread_db.so.  I think that got rid of
   the SIG32's, but...

Oddly, gdb doesn't seem to automatically load the shared libraries,
even though auto-solib-add is on.  I have to give the command
     shared
after hitting the breakpoint at main for the libraries to load,
else I get that SIG32 message.

Maybe I don't understand how shared libraries get loaded into
gdb.  I didn't think I should have to give the 'shared' command
normally.  Any idea what's up there?

And even then, I seem to get the SIGTRAP message referred to in
http://sources.redhat.com/ml/gdb/2003-03/msg00227.html
when I step a bit after hitting a breakpoint in a thread.
I tried applying the PREPARE_TO_PROCEED patch Daniel mentioned in
http://sources.redhat.com/ml/gdb/2003-03/msg00228.html,
and the original patch
http://sources.redhat.com/ml/gdb-patches/2002-08/msg01056.html
but neither of them seemed to apply cleanly against gdb-5.3.
Each had at least one reject.  I fixed up the rejects,
but the resulting debugger didn't work too well.

I'm sure my difficulties are because I'm sleepy, but perhaps
it's worth asking: should I stick with gdb5.3, or is a more
recent snapshot a better bet?  I'm running gdb on x86 linux,
and I'm running gdbserver on ppc405, ppc750, and sh4 linux.

Thanks,
Dan

-- 
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045


             reply	other threads:[~2003-04-08  6:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08  6:05 Dan Kegel [this message]
2003-04-08 12:52 ` 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=3E926917.1050900@kegel.com \
    --to=dank@kegel.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