multi-thread remote debugging i386-linux target (NEED HELP)

multi-thread remote debugging i386-linux target (NEED HELP)

[Peter Choi]

Hi,

  I compiled GDB6.3 host=i686-linux,
target=i386-linux.

  On the i386 target, run the compiled gdbserver, and
then break the middle of my test program. However, I
can only view 1 thread (main), all other thread cannot
be seen.

1. ldd gdbserver:
	libthread_db.so.1 => /lib/tls/libthread_db.so.1
(0x00996000)
	libc.so.6 => /lib/tls/libc.so.6 (0x0085b000)
	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00843000)

  It seems that libthread_db.so has been linked to
gdbserver.

But...
2. after breaking in the middle of my test program, I
examine the /proc/PID/maps:

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
00ae5000-00af2000 r-xp 00000000 03:02 985718    
/lib/tls/libpthread-0.60.so
00af2000-00af3000 rw-p 0000c000 03:02 985718    
/lib/tls/libpthread-0.60.so
00af3000-00af5000 rw-p 00000000 00:00 0
00c58000-00c5f000 r-xp 00000000 03:02 755708    
/lib/libgcc_s-3.3.2-20031023.so.1
00c5f000-00c60000 rw-p 00006000 03:02 755708    
/lib/libgcc_s-3.3.2-20031023.so.1
08048000-08049000 r-xp 00000000 03:05 1558879   
/home/pchoi/dev/test
08049000-0804a000 rw-p 00000000 03:05 1558879   
/home/pchoi/dev/test
099c9000-099ea000 rw-p 00000000 00:00 0
bc37f000-bc380000 ---p 00000000 00:00 0
bc380000-bcd80000 rw-p 00001000 00:00 0
bcd80000-bcd81000 ---p 00000000 00:00 0
bcd81000-bd781000 rw-p 00001000 00:00 0
bd781000-bd782000 ---p 00000000 00:00 0
bd782000-be182000 rw-p 00001000 00:00 0
be182000-be183000 ---p 00000000 00:00 0
be183000-beb84000 rw-p 00001000 00:00 0
beb84000-beb85000 ---p 00000000 00:00 0
beb85000-bf586000 rw-p 00001000 00:00 0
bfe5b000-c0000000 rw-p fff03000 00:00 0

   It seems that libthread_db.so has not been invoked.

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.

Regards.
Peter Choi



		
__________________________________ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Daniel Jacobowitz]

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

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Peter Choi]

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

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Daniel Jacobowitz]

On Mon, Nov 21, 2005 at 06:22:57PM -0800, Peter Choi wrote:
>   But I still can't see other threads being created.
> So, what could be the possible problem???

Did you read the message I quoted, and try the suggestions in it?
Here it is again:

> >   http://sourceware.org/ml/gdb/2005-11/msg00366.html

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Peter Choi]

Hi,

1.   On my host, library files of my i386-linux target
residues under directory /lib so well. So, need to add
prefix by "solib-absolute-prefix".

2.  If I use "symb test" to load symbols from my test
program on my host, I can then break in the main
thread (But I can't see all other threads created).

  However, If I use "file test" to load my test
program on my host, I CANNOT break at all. It simply
halt at somewhere, not sending/receiving any debug
packet at all. After all, it cannot stop at the end of
my test program too.

  Please advise what can possibly go wrong. Thank you
for your attention.


  

Regards.
Peter Choi


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

> On Mon, Nov 21, 2005 at 06:22:57PM -0800, Peter Choi
> wrote:
> >   But I still can't see other threads being
> created.
> > So, what could be the possible problem???
> 
> Did you read the message I quoted, and try the
> suggestions in it?
> Here it is again:
> 
> > >  
> http://sourceware.org/ml/gdb/2005-11/msg00366.html
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery, LLC
> 



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Daniel Jacobowitz]

On Mon, Nov 21, 2005 at 11:23:18PM -0800, Peter Choi wrote:
> Hi,
> 
> 1.   On my host, library files of my i386-linux target
> residues under directory /lib so well. So, need to add
> prefix by "solib-absolute-prefix".

Are the host and target running exactly the same libraries?

> 2.  If I use "symb test" to load symbols from my test
> program on my host, I can then break in the main
> thread (But I can't see all other threads created).
> 
>   However, If I use "file test" to load my test
> program on my host, I CANNOT break at all. It simply
> halt at somewhere, not sending/receiving any debug
> packet at all. After all, it cannot stop at the end of
> my test program too.
> 
>   Please advise what can possibly go wrong. Thank you
> for your attention.

Please post a session transcript, including "set debug remote 1", so
that we can see what happened.


-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Peter Choi]

Hi,

1. Yes, the host and target runs exactly the same
 libraries

2. How can I capture the debugger output to a file???

  Please advise. Thank you for your attention.

Regards.
Peter Choi

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

> On Mon, Nov 21, 2005 at 11:23:18PM -0800, Peter Choi
> wrote:
> > Hi,
> > 
> > 1.   On my host, library files of my i386-linux
> target
> > residues under directory /lib so well. So, need to
> add
> > prefix by "solib-absolute-prefix".
> 
> Are the host and target running exactly the same
> libraries?
> 
> > 2.  If I use "symb test" to load symbols from my
> test
> > program on my host, I can then break in the main
> > thread (But I can't see all other threads
> created).
> > 
> >   However, If I use "file test" to load my test
> > program on my host, I CANNOT break at all. It
> simply
> > halt at somewhere, not sending/receiving any debug
> > packet at all. After all, it cannot stop at the
> end of
> > my test program too.
> > 
> >   Please advise what can possibly go wrong. Thank
> you
> > for your attention.
> 
> Please post a session transcript, including "set
> debug remote 1", so
> that we can see what happened.
> 
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery, LLC
> 



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Daniel Jacobowitz]

On Tue, Nov 22, 2005 at 05:28:33PM -0800, Peter Choi wrote:
> Hi,
> 
> 1. Yes, the host and target runs exactly the same
>  libraries
> 
> 2. How can I capture the debugger output to a file???
> 
>   Please advise. Thank you for your attention.

Any way you want.  I use the "script" program.


-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Peter Choi]

Hi,

1. Yes, the host and target running exactly the same
 libraries


2. Protocol packets are captured as follows:

Breakpoint 1 at 0x8048527: file test.c, line 21.
Remote debugging using 10.247.1.237:2345
Sending packet: $Hc-1#09...Ack
Packet received: OK
Sending packet: $qC#b4...Ack
Packet received: 
Sending packet: $qOffsets#4b...Ack
Packet received: 
Sending packet: $?#3f...Ack
Packet received:
T0505:00000000;04:108df4bf;08:503c8400;
Sending packet: $m843c50,8#38...Ack
Packet received: 89e0e83900000089
Sending packet: $m843c50,7#37...Ack
Packet received: 89e0e839000000
0x00843c50 in ?? ()
Continuing.
Sending packet: $Z0,8048527,1#85...Ack
Packet received: 
Packet Z0 (software-breakpoint) is NOT supported
Sending packet: $m8048527,1#3c...Ack
Packet received: 83
Sending packet: $X8048527,0:#60...Ack
Packet received: 
binary downloading NOT suppported by target
Sending packet: $M8048527,1:cc#1c...Ack
Packet received: OK
Sending packet: $vCont?#49...Ack
Packet received: vCont;c;C;s;S
Packet vCont (verbose-resume) is supported
Sending packet: $vCont;c#a8...Ack
Packet received:
T0505:888cf4bf;04:508cf4bf;08:28850408;
Sending packet: $Hg0#df...Ack
Packet received: OK
Sending packet: $p0#a0...Ack
Packet received: 
Sending packet: $g#67...Ack
Packet received:
5c8cf4bf08ebdcbc0000000098099900508cf4bf888cf4bf148df4bf1c8df4bf2885040802020000230000002b0000002b0000002b000000000000003300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f03000000000000ffff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000801f0000ffffffff
Sending packet: $P8=27850408#67...Ack
Packet received: 
Sending packet:
$G5c8cf4bf08ebdcbc0000000098099900508cf4bf888cf4bf148df4bf1c8df4bf2785040802020000230000002b0000002b0000002b000000000000003300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f03000000000000ffff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000801f0000ffffffff#5b...Ack
Packet received: OK
Sending packet: $M8048527,1:83#c1...Ack
Packet received: OK

Breakpoint 1, main (Sending packet:
$mbff48c90,4#33...Ack
Packet received: 01000000
argc=1, Sending packet: $mbff48c94,4#37...Ack
Packet received: 148df4bf
argv=0xbff48d14) at test.c:21
21	  sleep(5);
Sending packet: $qfThreadInfo#bb...Ack
Packet received: mff3
Sending packet: $qsThreadInfo#c8...Ack
Packet received: l
  1 Thread 4083Sending packet:
$qThreadExtraInfo,ff3#84...Ack
Packet received: 
Sending packet: $qP0000001f0000000000000ff3#e7...Ack
Packet received: 
  Sending packet: $Hgff3#ae...Ack
Packet received: OK
Sending packet: $g#67...Ack
Packet received:
5c8cf4bf08ebdcbc0000000098099900508cf4bf888cf4bf148df4bf1c8df4bf2785040802020000230000002b0000002b0000002b000000000000003300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f03000000000000ffff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000801f0000ffffffff
main (Sending packet: $mbff48c90,4#33...Ack
Packet received: 01000000
argc=1, Sending packet: $mbff48c94,4#37...Ack
Packet received: 148df4bf
argv=0xbff48d14) at test.c:21
Sending packet: $Hg0#df...Ack
Packet received: OK
Sending packet: $g#67...Ack
Packet received:
5c8cf4bf08ebdcbc0000000098099900508cf4bf888cf4bf148df4bf1c8df4bf2785040802020000230000002b0000002b0000002b000000000000003300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f03000000000000ffff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000801f0000ffffffff
#0  main (Sending packet: $mbff48c90,4#33...Ack
Packet received: 01000000
argc=1, Sending packet: $mbff48c94,4#37...Ack
Packet received: 148df4bf
argv=0xbff48d14) at test.c:21


  Pls advise. Thank you for  your attention.

Regards.
Peter Choi

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

> On Mon, Nov 21, 2005 at 11:23:18PM -0800, Peter Choi
> wrote:
> > Hi,
> > 
> > 1.   On my host, library files of my i386-linux
> target
> > residues under directory /lib so well. So, need to
> add
> > prefix by "solib-absolute-prefix".
> 
> Are the host and target running exactly the same
> libraries?
> 
> > 2.  If I use "symb test" to load symbols from my
> test
> > program on my host, I can then break in the main
> > thread (But I can't see all other threads
> created).
> > 
> >   However, If I use "file test" to load my test
> > program on my host, I CANNOT break at all. It
> simply
> > halt at somewhere, not sending/receiving any debug
> > packet at all. After all, it cannot stop at the
> end of
> > my test program too.
> > 
> >   Please advise what can possibly go wrong. Thank
> you
> > for your attention.
> 
> Please post a session transcript, including "set
> debug remote 1", so
> that we can see what happened.
> 
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery, LLC
> 



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Daniel Jacobowitz]

On Tue, Nov 22, 2005 at 06:03:45PM -0800, Peter Choi wrote:
> Hi,
> 
> 1. Yes, the host and target running exactly the same
>  libraries
> 
> 
> 2. Protocol packets are captured as follows:

I said you needed to use "file", and make sure that "info shared"
worked.  You said that when you used "file" you couldn't breakpoint at
all.  That's what you needed to post a transcript of.

Please send the entire sequence of commands, from first starting GDB.


-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Peter Choi]

Hi,

  Use "file test" this time. Exact commands I use in
host side gdb is as follows:

  file test
  b test.c:21
  set remotetimeout 60
  set debug remote 1
  target remote 10.247.1.237:2345
  c

  Below is what I got:

Reading symbols from /home/pchoi/dev/test...done.
Breakpoint 1 at 0x8048527: file test.c, line 21.
No shared libraries loaded at this time.
Remote debugging using 10.247.1.237:2345
Sending packet: $Hc-1#09...Ack
Packet received: OK
Sending packet: $qC#b4...Ack
Packet received: 
Sending packet: $qOffsets#4b...Ack
Packet received: 
Sending packet: $?#3f...Ack
Packet received:
T0505:00000000;04:80d9e9bf;08:503c8400;
Sending packet: $m843c50,8#38...Ack
Packet received: 89e0e83900000089
Sending packet: $m843c50,7#37...Ack
Packet received: 89e0e839000000
0x00843c50 in ?? ()
Sending packet: $m8049664,d0#a2...Ack
Packet received:
0100000001000000010000004e0000000c0000006c8304080d000000188604080400000048810408050000002482040806000000848104080a000000a90000000b000000100000001500000000000000030000004897040802000000300000001400000011000000170000003c830408110000003483040812000000080000001300000008000000feffff6fe4820408ffffff6f02000000f0ffff6fce820408000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Sending packet: $qSymbol::#5b...Ack
Packet received: qSymbol:6e70746c5f76657273696f6e
Packet qSymbol (symbol-lookup) is supported
Sending packet:
$qSymbol::6e70746c5f76657273696f6e#4d...Ack
Packet received: OK
Continuing.
Sending packet: $Z0,8048527,1#85...Ack
Packet received: 
Packet Z0 (software-breakpoint) is NOT supported
Sending packet: $m8048527,1#3c...Ack
Packet received: 83
Sending packet: $X8048527,0:#60...Ack
Packet received: 
binary downloading NOT suppported by target
Sending packet: $M8048527,1:cc#1c...Ack
Packet received: OK
Sending packet: $m84fea0,1#92...Ack
Packet received: 55
Sending packet: $M84fea0,1:cc#72...Ack
Packet received: OK
Sending packet: $vCont?#49...Ack
Packet received: vCont;c;C;s;S
Packet vCont (verbose-resume) is supported
Sending packet: $vCont;c#a8...Ack
Packet received:
T0505:fcd6e9bf;04:2cd5e9bf;08:a1fe8400;
Sending packet: $Hg0#df...Ack
Packet received: OK
Sending packet: $p0#a0...Ack
Packet received: 
Sending packet: $g#67...Ack
Packet received:
000000000485850044878500048585002cd5e9bffcd6e9bf5887850006000000a1fe840046020000230000002b0000002b0000002b000000000000003300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f03000000000000ffff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000801f0000ffffffff
Sending packet: $P8=a0fe8400#ed...Ack
Packet received: 
Sending packet:
$G000000000485850044878500048585002cd5e9bffcd6e9bf5887850006000000a0fe840046020000230000002b0000002b0000002b000000000000003300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f03000000000000ffff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000801f0000ffffffff#95...Ack
Packet received: OK
Sending packet: $M8048527,1:83#c1...Ack
Packet received: OK
Sending packet: $M84fea0,1:55#16...Ack
Packet received: OK
Sending packet: $m8049664,d0#a2...Ack
Packet received:
0100000001000000010000004e0000000c0000006c8304080d000000188604080400000048810408050000002482040806000000848104080a000000a90000000b000000100000001500000044878500030000004897040802000000300000001400000011000000170000003c830408110000003483040812000000080000001300000008000000feffff6fe4820408ffffff6f02000000f0ffff6fce820408000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Sending packet: $m858748,4#15...Ack
Packet received: 58878500
Sending packet: $m858758,14#47...Ack
Packet received:
00000000b25d85006496040800005bbf00000000
Sending packet: $mbf5b0000,14#1d...Ack
Packet received:
00000000b88d8500c42baf0080025bbf58878500
Sending packet: $m858db8,4#70...Ack
Packet received: 2f6c6962
Sending packet: $m858dbc,4#9b...Ack
Packet received: 2f746c73
Sending packet: $m858dc0,4#69...Ack
Packet received: 2f6c6962
Sending packet: $m858dc4,4#6d...Ack
Packet received: 70746872
Sending packet: $m858dc8,4#71...Ack
Packet received: 6561642e
Sending packet: $m858dcc,4#9c...Ack
Packet received: 736f2e30
Sending packet: $m858dd0,4#6a...Ack
Packet received: 00000000
Sending packet: $mbf5b0280,14#27...Ack
Packet received:
0000000068025bbfa4089900ec81850000005bbf
Sending packet: $mbf5b0268,4#fc...Ack
Packet received: 2f6c6962
Sending packet: $mbf5b026c,4#27...Ack
Packet received: 2f746c73
Sending packet: $mbf5b0270,4#f5...Ack
Packet received: 2f6c6962
Sending packet: $mbf5b0274,4#f9...Ack
Packet received: 632e736f
Sending packet: $mbf5b0278,4#fd...Ack
Packet received: 2e360000
Sending packet: $m8581ec,14#9c...Ack
Packet received:
0000000014810408548485000000000080025bbf
Sending packet: $m8048114,4#37...Ack
Packet received: 2f6c6962
Sending packet: $m8048118,4#3b...Ack
Packet received: 2f6c642d
Sending packet: $m804811c,4#66...Ack
Packet received: 6c696e75
Sending packet: $m8048120,4#34...Ack
Packet received: 782e736f
Sending packet: $m8048124,4#38...Ack
Packet received: 2e320000
Sending packet: $qSymbol::#5b...Ack
Packet received: qSymbol:6e70746c5f76657273696f6e
Sending packet:
$qSymbol:af0ae0:6e70746c5f76657273696f6e#3a...Ack
Packet received:
qSymbol:5f5f6e70746c5f746872656164735f6576656e7473
Sending packet:
$qSymbol:af4e40:5f5f6e70746c5f746872656164735f6576656e7473#2c...Ack
Packet received:
qSymbol:5f7468726561645f64625f73697a656f665f74645f7468725f6576656e74735f74
Sending packet:
$qSymbol:af0cf0:5f7468726561645f64625f73697a656f665f74645f7468725f6576656e74735f74#f1...Ack
Packet received:
qSymbol:5f7468726561645f64625f74645f7468725f6576656e74735f745f6576656e745f62697473
Sending packet:
$qSymbol:af0cf4:5f7468726561645f64625f74645f7468725f6576656e74735f745f6576656e745f62697473#a1...Ack
Packet received:
qSymbol:5f5f6e70746c5f6372656174655f6576656e74
Sending packet:
$qSymbol:ae9690:5f5f6e70746c5f6372656174655f6576656e74#2e...Ack
Packet received: qSymbol:5f5f737461636b5f75736572
Sending packet:
$qSymbol:af2e24:5f5f737461636b5f75736572#d7...Ack
Packet received:
qSymbol:5f7468726561645f64625f6c6973745f745f6e657874
Sending packet:
$qSymbol:af0cd8:5f7468726561645f64625f6c6973745f745f6e657874#d0...Ack
Packet received:
qSymbol:5f7468726561645f64625f636f6e73745f7468726561645f61726561
Sending packet:
$qSymbol::5f7468726561645f64625f636f6e73745f7468726561645f61726561#47...Ack
Packet received:
qSymbol:5f7468726561645f64625f72656769737465723332
Sending packet:
$qSymbol::5f7468726561645f64625f72656769737465723332#a0...Ack
Packet received:
qSymbol:5f7468726561645f64625f726567697374657233325f7468726561645f61726561
Sending packet:
$qSymbol:af0dac:5f7468726561645f64625f726567697374657233325f7468726561645f61726561#15...Ack
Packet received:
qSymbol:5f7468726561645f64625f73697a656f665f70746872656164
Sending packet:
$qSymbol:af0c40:5f7468726561645f64625f73697a656f665f70746872656164#9e...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f7370656369666963
Sending packet:
$qSymbol:af0c98:5f7468726561645f64625f707468726561645f7370656369666963#1f...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f7363686564706f6c696379
Sending packet:
$qSymbol:af0c80:5f7468726561645f64625f707468726561645f7363686564706f6c696379#b8...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f7363686564706172616d5f73636865645f7072696f72697479
Sending packet:
$qSymbol:af0c8c:5f7468726561645f64625f707468726561645f7363686564706172616d5f73636865645f7072696f72697479#19...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f746964
Sending packet:
$qSymbol:af0c5c:5f7468726561645f64625f707468726561645f746964#32...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f63616e63656c68616e646c696e67
Sending packet:
$qSymbol:af0c74:5f7468726561645f64625f707468726561645f63616e63656c68616e646c696e67#83...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f7265706f72745f6576656e7473
Sending packet:
$qSymbol:af0c50:5f7468726561645f64625f707468726561645f7265706f72745f6576656e7473#b4...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f73746172745f726f7574696e65
Sending packet:
$qSymbol:af0c68:5f7468726561645f64625f707468726561645f73746172745f726f7574696e65#c0...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f6576656e746275665f6576656e746d61736b5f6576656e745f62697473
Sending packet:
$qSymbol:af0cbc:5f7468726561645f64625f707468726561645f6576656e746275665f6576656e746d61736b5f6576656e745f62697473#b6...Ack
Packet received: qSymbol:737461636b5f75736564
Sending packet:
$qSymbol:af2bb8:737461636b5f75736564#d3...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f6c697374
Sending packet:
$qSymbol:af0c44:5f7468726561645f64625f707468726561645f6c697374#9b...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f6576656e74627566
Sending packet:
$qSymbol:af0ca4:5f7468726561645f64625f707468726561645f6576656e74627566#74...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f6576656e746275665f6576656e746d61736b
Sending packet:
$qSymbol:af0cb0:5f7468726561645f64625f707468726561645f6576656e746275665f6576656e746d61736b#58...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f6e6578746576656e74
Sending packet:
$qSymbol:af0cc8:5f7468726561645f64625f707468726561645f6e6578746576656e74#1a...Ack
Packet received:
qSymbol:5f7468726561645f64625f73697a656f665f6c6973745f74
Sending packet:
$qSymbol:af0cd4:5f7468726561645f64625f73697a656f665f6c6973745f74#d0...Ack
Packet received:
qSymbol:5f7468726561645f64625f6c6973745f745f70726576
Sending packet:
$qSymbol:af0ce4:5f7468726561645f64625f6c6973745f745f70726576#95...Ack
Packet received:
qSymbol:5f7468726561645f64625f73697a656f665f74645f6576656e746275665f74
Sending packet:
$qSymbol:af0d00:5f7468726561645f64625f73697a656f665f74645f6576656e746275665f74#b5...Ack
Packet received:
qSymbol:5f7468726561645f64625f74645f6576656e746275665f745f6576656e746e756d
Sending packet:
$qSymbol:af0d04:5f7468726561645f64625f74645f6576656e746275665f745f6576656e746e756d#bf...Ack
Packet received:
qSymbol:5f7468726561645f64625f74645f6576656e746275665f745f6576656e7464617461
Sending packet:
$qSymbol:af0d10:5f7468726561645f64625f74645f6576656e746275665f745f6576656e7464617461#be...Ack
Packet received:
qSymbol:5f5f6e70746c5f64656174685f6576656e74
Sending packet:
$qSymbol:ae96a0:5f5f6e70746c5f64656174685f6576656e74#f1...Ack
Packet received:
qSymbol:5f5f6e70746c5f6e74687265616473
Sending packet:
$qSymbol:af2ba8:5f5f6e70746c5f6e74687265616473#a9...Ack
Packet received:
qSymbol:5f7468726561645f64625f5f5f6e70746c5f6e74687265616473
Sending packet:
$qSymbol:af0d1c:5f7468726561645f64625f5f5f6e70746c5f6e74687265616473#c5...Ack
Packet received:
qSymbol:5f5f6e70746c5f6c6173745f6576656e74
Sending packet:
$qSymbol:af4e48:5f5f6e70746c5f6c6173745f6576656e74#b7...Ack
Packet received:
qSymbol:5f7468726561645f64625f5f5f6e70746c5f6c6173745f6576656e74
Sending packet:
$qSymbol:af0d28:5f7468726561645f64625f5f5f6e70746c5f6c6173745f6576656e74#d1...Ack
Packet received: qSymbol:5f5f707468726561645f6b657973
Sending packet:
$qSymbol:af2e40:5f5f707468726561645f6b657973#b0...Ack
Packet received:
qSymbol:5f7468726561645f64625f5f5f707468726561645f6b657973
Sending packet:
$qSymbol:af0d34:5f7468726561645f64625f5f5f707468726561645f6b657973#d1...Ack
Packet received:
qSymbol:5f7468726561645f64625f73697a656f665f707468726561645f6b65795f737472756374
Sending packet:
$qSymbol:af0d40:5f7468726561645f64625f73697a656f665f707468726561645f6b65795f737472756374#c6...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f6b65795f7374727563745f736571
Sending packet:
$qSymbol:af0d44:5f7468726561645f64625f707468726561645f6b65795f7374727563745f736571#23...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f6b65795f7374727563745f6465737472
Sending packet:
$qSymbol:af0d50:5f7468726561645f64625f707468726561645f6b65795f7374727563745f6465737472#f6...Ack
Packet received:
qSymbol:5f7468726561645f64625f73697a656f665f707468726561645f6b65795f64617461
Sending packet:
$qSymbol:af0d5c:5f7468726561645f64625f73697a656f665f707468726561645f6b65795f64617461#1f...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f6b65795f646174615f736571
Sending packet:
$qSymbol:af0d60:5f7468726561645f64625f707468726561645f6b65795f646174615f736571#46...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f6b65795f646174615f64617461
Sending packet:
$qSymbol:af0d6c:5f7468726561645f64625f707468726561645f6b65795f646174615f64617461#df...Ack
Packet received:
qSymbol:5f7468726561645f64625f73697a656f665f707468726561645f6b65795f646174615f6c6576656c32
Sending packet:
$qSymbol:af0d78:5f7468726561645f64625f73697a656f665f707468726561645f6b65795f646174615f6c6576656c32#6b...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f6b65795f646174615f6c6576656c325f64617461
Sending packet:
$qSymbol:af0d7c:5f7468726561645f64625f707468726561645f6b65795f646174615f6c6576656c325f64617461#55...Ack
Packet received:
qSymbol:5f7468726561645f64625f6c696e6b5f6d61705f6c5f746c735f6d6f646964
Sending packet:
$qSymbol:af0d88:5f7468726561645f64625f6c696e6b5f6d61705f6c5f746c735f6d6f646964#d6...Ack
Packet received:
qSymbol:5f7468726561645f64625f6474765f647476
Sending packet:
$qSymbol:af0d94:5f7468726561645f64625f6474765f647476#63...Ack
Packet received:
qSymbol:5f7468726561645f64625f707468726561645f64747670
Sending packet:
$qSymbol:af0da0:5f7468726561645f64625f707468726561645f64747670#91...Ack
Packet received:
qSymbol:5f7468726561645f64625f636f6e73745f7468726561645f61726561
Sending packet:
$qSymbol::5f7468726561645f64625f636f6e73745f7468726561645f61726561#47...Ack
Packet received:
qSymbol:5f7468726561645f64625f72656769737465723634
Sending packet:
$qSymbol::5f7468726561645f64625f72656769737465723634#a5...Ack
Packet received:
qSymbol:5f7468726561645f64625f72656769737465723332
Sending packet:
$qSymbol::5f7468726561645f64625f72656769737465723332#a0...Ack
Packet received:
qSymbol:5f7468726561645f64625f726567697374657236345f7468726561645f61726561
Sending packet:
$qSymbol:af0db8:5f7468726561645f64625f726567697374657236345f7468726561645f61726561#f0...Ack
Packet received: OK
Sending packet: $qSymbol::#5b...Ack
Packet received: OK
Sending packet: $qSymbol::#5b...Ack
Packet received: OK
Sending packet: $vCont;s#b8...Ack
Packet received:
T0505:fcd6e9bf;04:28d5e9bf;08:a1fe8400;thread:bf5b0b40;
[New Thread -1084552384]
Sending packet: $g#67...Ack
Packet received:
0000000004858500448785000485850028d5e9bffcd6e9bf5887850006000000a1fe840046030000230000002b0000002b0000002b000000000000003300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f03000000000000ffff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000801f0000ffffffff
Sending packet: $m8048527,1#3c...Ack
Packet received: 83
Sending packet: $M8048527,1:cc#1c...Ack
Packet received: OK
Sending packet: $m84fea0,1#92...Ack
Packet received: 55
Sending packet: $M84fea0,1:cc#72...Ack
Packet received: OK
Sending packet: $vCont;c#a8...Ack
Packet received:
T0505:74d9e9bf;04:28d9e9bf;08:a1fe8400;thread:bf5b0b40;
Sending packet: $g#67...Ack
Packet received:
4487850004858500448785000485850028d9e9bf74d9e9bf0000000000000000a1fe840006020000230000002b0000002b0000002b000000000000003300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f03000000000000ffff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000801f0000ffffffff
Sending packet:
$G4487850004858500448785000485850028d9e9bf74d9e9bf0000000000000000a0fe840006020000230000002b0000002b0000002b000000000000003300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f03000000000000ffff000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000801f0000ffffffff#04...Ack
Packet received: OK
Sending packet: $M8048527,1:83#c1...Ack
Packet received: OK
Sending packet: $M84fea0,1:55#16...Ack
Packet received: OK
Sending packet: $m858748,4#15...Ack
Packet received: 58878500
Sending packet: $m858758,14#47...Ack
Packet received:
00000000b25d85006496040800005bbf00000000
Sending packet: $mbf5b0000,14#1d...Ack
Packet received:
00000000b88d8500c42baf0080025bbf58878500
Sending packet: $m858db8,4#70...Ack
Packet received: 2f6c6962
Sending packet: $m858dbc,4#9b...Ack
Packet received: 2f746c73
Sending packet: $m858dc0,4#69...Ack
Packet received: 2f6c6962
Sending packet: $m858dc4,4#6d...Ack
Packet received: 70746872
Sending packet: $m858dc8,4#71...Ack
Packet received: 6561642e
Sending packet: $m858dcc,4#9c...Ack
Packet received: 736f2e30
Sending packet: $m858dd0,4#6a...Ack
Packet received: 00000000
Sending packet: $mbf5b0280,14#27...Ack
Packet received:
0000000068025bbfa4089900ec81850000005bbf
Sending packet: $mbf5b0268,4#fc...Ack
Packet received: 2f6c6962
Sending packet: $mbf5b026c,4#27...Ack
Packet received: 2f746c73
Sending packet: $mbf5b0270,4#f5...Ack
Packet received: 2f6c6962
Sending packet: $mbf5b0274,4#f9...Ack
Packet received: 632e736f
Sending packet: $mbf5b0278,4#fd...Ack
Packet received: 2e360000
Sending packet: $m8581ec,14#9c...Ack
Packet received:
0000000014810408548485000000000080025bbf
Sending packet: $m8048114,4#37...Ack
Packet received: 2f6c6962
Sending packet: $m8048118,4#3b...Ack
Packet received: 2f6c642d
Sending packet: $m804811c,4#66...Ack
Packet received: 6c696e75
Sending packet: $m8048120,4#34...Ack
Packet received: 782e736f
Sending packet: $m8048124,4#38...Ack
Packet received: 2e320000
Sending packet: $vCont;s:bf5b0b40#47...Ack


  Pls advise. Thank you for your attention.

Regards.
Peter Choi

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

> On Tue, Nov 22, 2005 at 06:03:45PM -0800, Peter Choi
> wrote:
> > Hi,
> > 
> > 1. Yes, the host and target running exactly the
> same
> >  libraries
> > 
> > 
> > 2. Protocol packets are captured as follows:
> 
> I said you needed to use "file", and make sure that
> "info shared"
> worked.  You said that when you used "file" you
> couldn't breakpoint at
> all.  That's what you needed to post a transcript
> of.
> 
> Please send the entire sequence of commands, from
> first starting GDB.
> 
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery, LLC
> 



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Daniel Jacobowitz]

On Tue, Nov 22, 2005 at 10:18:40PM -0800, Peter Choi wrote:
> Hi,
> 
>   Use "file test" this time. Exact commands I use in
> host side gdb is as follows:
> 
>   file test
>   b test.c:21
>   set remotetimeout 60
>   set debug remote 1
>   target remote 10.247.1.237:2345
>   c
> 
>   Below is what I got:

Sorry, you're going to have to debug gdbserver yourself.  Did it print
out any helpful output, or just hang?


-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Peter Choi]

Hi,

  GDBserver did not show any output at all. 

  To debug gdbserver, where should break at???? It
seems that it cannot display protocol packets on its
side.

Regards.
Peter Choi


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

> On Tue, Nov 22, 2005 at 10:18:40PM -0800, Peter Choi
> wrote:
> > Hi,
> > 
> >   Use "file test" this time. Exact commands I use
> in
> > host side gdb is as follows:
> > 
> >   file test
> >   b test.c:21
> >   set remotetimeout 60
> >   set debug remote 1
> >   target remote 10.247.1.237:2345
> >   c
> > 
> >   Below is what I got:
> 
> Sorry, you're going to have to debug gdbserver
> yourself.  Did it print
> out any helpful output, or just hang?
> 
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery, LLC
> 



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Daniel Jacobowitz]

On Wed, Nov 23, 2005 at 06:05:10PM -0800, Peter Choi wrote:
> Hi,
> 
>   GDBserver did not show any output at all. 
> 
>   To debug gdbserver, where should break at???? It
> seems that it cannot display protocol packets on its
> side.

It can if you set the appropriate variable in the source, I think it's
debug_threads.  You'll have to figure the rest out on your own, since
we can't figure out your problem.


-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: multi-thread remote debugging i386-linux target (NEED HELP)

[Peter Choi]

Hi,

  I set "debug_thread" as 1 and recompile gdbserver.
After I run the same scenario and I got the following
logged on the target side:

Process test created; pid = 21524
Got an event from 21524 (57f)
stop pc (before any decrement) is 00843c50
stop pc (before any decrement) is 00843c50
Hit a (non-reinsert) breakpoint.
Listening on port 2345
Remote debugging from host 10.247.1.237
Writing ffffffcc to 08048527
Writing ffffffcc to 0084fea0
Resuming, no pending status
Resuming process 21524 (continue, signal 0, stop not
expected)
  stop pc (before any decrement) is 00843c50
Got an event from 21524 (57f)
stop pc (before any decrement) is 0084fea1
stop pc (before any decrement) is 0084fea1
Hit a (non-reinsert) breakpoint.
Writing ffffff83 to 08048527
Writing 55 to 0084fea0
Writing ffffff80 to 00af4e40
Writing ffffffcc to 00ae9690
Writing 01 to bf518d20
Resuming, no pending status
Resuming process 21524 (step, signal 0, stop not
expected)
Checking for breakpoint.
stop pc (before any decrement) is 0084fea1
Removed breakpoint.
set pc to 0084fea0
  stop pc (before any decrement) is 0084fea0
Got an event from 21524 (57f)
stop pc (before any decrement) is 0084fea1
stop pc (before any decrement) is 0084fea1
Hit a (non-reinsert) breakpoint.
Writing resume reply for -1085174976

Writing ffffffcc to 08048527
Writing ffffffcc to 0084fea0
Resuming, no pending status
Resuming process 21524 (continue, signal 0, stop not
expected)
  stop pc (before any decrement) is 0084fea1
Got an event from 21524 (57f)
stop pc (before any decrement) is 0084fea1
stop pc (before any decrement) is 0084fea1
Hit a (non-reinsert) breakpoint.
Writing resume reply for -1085174976

Writing ffffff83 to 08048527
Writing 55 to 0084fea0
Resuming, no pending status
Resuming, no pending status
Resuming process 21524 (continue, signal 0, stop not
expected)
Checking for breakpoint.
stop pc (before any decrement) is 0084fea0
Ignoring, PC was changed.
  stop pc (before any decrement) is 0084fea0
Got an event from 21524 (57f)
stop pc (before any decrement) is 00ae9691
stop pc (before any decrement) is 00ae9691
Hit a (non-reinsert) breakpoint.
Thread creation event.
Writing 00 to bf517dbc
Writing 00 to 00af4e48
Attaching to thread -1085178960 (LWP 21526)
Writing 01 to bf517d90
Writing 55 to 00ae9690
Resuming process 21524 (step, signal 0, stop not
expected)
  pending reinsert at 00ae9690Checking for breakpoint.
stop pc (before any decrement) is 00ae9691
Removed breakpoint.
set pc to 00ae9690
  stop pc (before any decrement) is 00ae9690
Got an event from 21524 (57f)
stop pc (before any decrement) is 00ae9691
stop pc (before any decrement) is 00ae9691
Reinserted breakpoint.
Writing ffffffcc to 00ae9690
Resuming process 21524 (continue, signal 0, stop not
expected)
  stop pc (before any decrement) is 00ae9691
Got an event from 21524 (57f)
stop pc (before any decrement) is 00ae9691
stop pc (before any decrement) is 00ae9691
Hit a (non-reinsert) breakpoint.
Thread creation event.
Writing 00 to beb16dbc
Writing 00 to 00af4e48
Attaching to thread -1095668816 (LWP 21527)
Writing 01 to beb16d90
Writing 55 to 00ae9690
Resuming process 21524 (step, signal 0, stop not
expected)
  pending reinsert at 00ae9690Checking for breakpoint.
stop pc (before any decrement) is 00ae9691
Removed breakpoint.
set pc to 00ae9690
  stop pc (before any decrement) is 00ae9690
Got an event from 21524 (57f)
stop pc (before any decrement) is 00ae9691
stop pc (before any decrement) is 00ae9691
Reinserted breakpoint.
Writing ffffffcc to 00ae9690
Resuming process 21524 (continue, signal 0, stop not
expected)
  stop pc (before any decrement) is 00ae9691
Got an event from 21524 (57f)
stop pc (before any decrement) is 00ae9691
stop pc (before any decrement) is 00ae9691
Hit a (non-reinsert) breakpoint.
Thread creation event.
Writing 00 to be115dbc
Writing 00 to 00af4e48
Attaching to thread -1106158672 (LWP 21528)
Writing 01 to be115d90
Writing 55 to 00ae9690
Resuming process 21524 (step, signal 0, stop not
expected)
  pending reinsert at 00ae9690Checking for breakpoint.
stop pc (before any decrement) is 00ae9691
Removed breakpoint.
set pc to 00ae9690
  stop pc (before any decrement) is 00ae9690
Got an event from 21524 (57f)
stop pc (before any decrement) is 00ae9691
stop pc (before any decrement) is 00ae9691
Reinserted breakpoint.
Writing ffffffcc to 00ae9690
Resuming process 21524 (continue, signal 0, stop not
expected)
  stop pc (before any decrement) is 00ae9691
Got an event from 21524 (57f)
stop pc (before any decrement) is 00ae9691
stop pc (before any decrement) is 00ae9691
Hit a (non-reinsert) breakpoint.
Thread creation event.
Writing 00 to bd714dbc
Writing 00 to 00af4e48
Attaching to thread -1116648528 (LWP 21529)
Writing 01 to bd714d90
Writing 55 to 00ae9690
Resuming process 21524 (step, signal 0, stop not
expected)
  pending reinsert at 00ae9690Checking for breakpoint.
stop pc (before any decrement) is 00ae9691
Removed breakpoint.
set pc to 00ae9690
  stop pc (before any decrement) is 00ae9690
Got an event from 21524 (57f)
stop pc (before any decrement) is 00ae9691
stop pc (before any decrement) is 00ae9691
Reinserted breakpoint.
Writing ffffffcc to 00ae9690
Resuming process 21524 (continue, signal 0, stop not
expected)
  stop pc (before any decrement) is 00ae9691
Got an event from 21524 (57f)
stop pc (before any decrement) is 00ae9691
stop pc (before any decrement) is 00ae9691
Hit a (non-reinsert) breakpoint.
Thread creation event.
Writing 00 to bcd13dbc
Writing 00 to 00af4e48
Attaching to thread -1127138384 (LWP 21530)
Writing 01 to bcd13d90
Writing 55 to 00ae9690
Resuming process 21524 (step, signal 0, stop not
expected)
  pending reinsert at 00ae9690Checking for breakpoint.
stop pc (before any decrement) is 00ae9691
Removed breakpoint.
set pc to 00ae9690
  stop pc (before any decrement) is 00ae9690
Got an event from 21524 (57f)
stop pc (before any decrement) is 00ae9691
stop pc (before any decrement) is 00ae9691
Reinserted breakpoint.
Writing ffffffcc to 00ae9690
Resuming process 21524 (continue, signal 0, stop not
expected)
  stop pc (before any decrement) is 00ae9691
Got an event from 21526 (137f)
stop pc (before any decrement) is 00843c32
Expected stop.
Resuming process 21526 (continue, signal 0, stop not
expected)
  stop pc (before any decrement) is 00843c32
Got an event from 21527 (137f)
stop pc (before any decrement) is 00843c32
Expected stop.
Resuming process 21527 (continue, signal 0, stop not
expected)
  stop pc (before any decrement) is 00843c32
Got an event from 21528 (137f)
stop pc (before any decrement) is 00843c32
Expected stop.
Resuming process 21528 (continue, signal 0, stop not
expected)
  stop pc (before any decrement) is 00843c32
Got an event from 21529 (137f)
stop pc (before any decrement) is 00843c32
Expected stop.
Resuming process 21529 (continue, signal 0, stop not
expected)
  stop pc (before any decrement) is 00843c32
Got an event from 21530 (137f)
stop pc (before any decrement) is 00843c32
Expected stop.
Resuming process 21530 (continue, signal 0, stop not
expected)
  stop pc (before any decrement) is 00843c32
Hello World from 0!
Hello World from 1!
Hello World from 2!
Hello World from 3!
Hello World from 4!
Got an event from 21524 (0)
Thread -1085174976 (LWP 21524) exiting

  It seems it do report new threads are created and
attached.  
  I have set only 1 breakpoint on the main thread. But
it reported : "Hit a (non-reinsert) breakpoint"
several times, and sometimes it said "Removed
breakpoint" and "Reinserted breakpoint"! What do  it
mean by that????

  Pls advise. Thank you for your attention.  

Regards.
Peter Choi


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

> On Wed, Nov 23, 2005 at 06:05:10PM -0800, Peter Choi
> wrote:
> > Hi,
> > 
> >   GDBserver did not show any output at all. 
> > 
> >   To debug gdbserver, where should break at???? It
> > seems that it cannot display protocol packets on
> its
> > side.
> 
> It can if you set the appropriate variable in the
> source, I think it's
> debug_threads.  You'll have to figure the rest out
> on your own, since
> we can't figure out your problem.
> 
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery, LLC
> 



		
__________________________________ 
Yahoo! Music Unlimited 
Access over 1 million songs. Try it free. 
http://music.yahoo.com/unlimited/