Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Peter Choi <peter_tkchoi@yahoo.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: multi-thread remote debugging i386-linux target (NEED HELP)
Date: Tue, 22 Nov 2005 02:23:00 -0000	[thread overview]
Message-ID: <20051122022257.93913.qmail@web32901.mail.mud.yahoo.com> (raw)
In-Reply-To: <20051121051333.GA12327@nevyn.them.org>

Hi,

  Looking at the map of gdbserver :

00843000-00858000 r-xp 00000000 03:02 755706    
/lib/ld-2.3.2.so
00858000-00859000 rw-p 00015000 03:02 755706    
/lib/ld-2.3.2.so
0085b000-0098e000 r-xp 00000000 03:02 985716    
/lib/tls/libc-2.3.2.so
0098e000-00991000 rw-p 00132000 03:02 985716    
/lib/tls/libc-2.3.2.so
00991000-00994000 rw-p 00000000 00:00 0
00996000-0099b000 r-xp 00000000 03:02 983102    
/lib/tls/libthread_db-1.0.so
0099b000-0099c000 rw-p 00004000 03:02 983102    
/lib/tls/libthread_db-1.0.so
08048000-08053000 r-xp 00000000 03:05 412011    
/home/pchoi/work/tools/i386-linux/bin/gdbserver
08053000-08054000 rw-p 0000b000 03:05 412011    
/home/pchoi/work/tools/i386-linux/bin/gdbserver
08054000-08056000 rw-p 00000000 00:00 0
0964e000-0966f000 rw-p 00000000 00:00 0
bf56e000-bf56f000 rw-p 00000000 00:00 0
bff7a000-c0000000 rw-p fffdc000 00:00 0

  It seems it can load the libthread_db. So the path
should be correct.

  But I still can't see other threads being created.
So, what could be the possible problem???

  Pls advise. Thank you for your attention.

Regards.
Peter Choi


--- Daniel Jacobowitz <drow@false.org> wrote:

> On Sun, Nov 20, 2005 at 09:07:40PM -0800, Peter Choi
> wrote:
> > But...
> > 2. after breaking in the middle of my test
> program, I
> > examine the /proc/PID/maps:
> 
> You're looking at the map of your program. 
> libthread_db is in the
> address space of gdbserver.
> 
> > 3. I has tried "set debug remote 1" to examine the
> > remote protocol packets, but have no idea how
> shall
> > the expected packet look like??
> > 
> >   Please advise. Thank you for your attention.
> 
> I obviously need to write a troubleshooting guide
> for this.  I feel
> like I've walked a half-dozen people through it in
> the last two months,
> which is a sure sign the documentation needs to be
> improved.
> 
> Does any of this help?
> 
>   http://sourceware.org/ml/gdb/2005-11/msg00366.html
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery, LLC
> 



		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com


  reply	other threads:[~2005-11-22  2:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21  5:07 Peter Choi
2005-11-21  5:13 ` Daniel Jacobowitz
2005-11-22  2:23   ` Peter Choi [this message]
2005-11-22  4:51     ` Daniel Jacobowitz
2005-11-22  7:23       ` Peter Choi
2005-11-22 13:55         ` Daniel Jacobowitz
2005-11-23  1:30           ` Peter Choi
2005-11-23  2:03             ` Daniel Jacobowitz
2005-11-23  2:05           ` Peter Choi
2005-11-23  2:23             ` Daniel Jacobowitz
2005-11-23  8:36               ` Peter Choi
2005-11-23 13:54                 ` Daniel Jacobowitz
2005-11-24  2:24                   ` Peter Choi
2005-11-24  4:50                     ` Daniel Jacobowitz
2005-11-25  2:50                       ` Peter Choi

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=20051122022257.93913.qmail@web32901.mail.mud.yahoo.com \
    --to=peter_tkchoi@yahoo.com \
    --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