From: Daniel Jacobowitz <drow@mvista.com>
To: Frank van Eijkelenburg <frank.van.eijkelenburg@technolution.nl>
Cc: Gnu Debugger mailing list <gdb@sources.redhat.com>
Subject: Re: multithreaded remote debugging
Date: Fri, 17 Jan 2003 15:17:00 -0000 [thread overview]
Message-ID: <20030117151701.GA20207@nevyn.them.org> (raw)
In-Reply-To: <JJEILELDMJJENLCGJHOIMEDKCEAA.frank.van.eijkelenburg@technolution.nl>
On Fri, Jan 17, 2003 at 04:09:33PM +0100, Frank van Eijkelenburg wrote:
> libthread_db.so.1 is installed on the target. I have a copy of the
> application on the host. Actually its the same file as the target uses. I
> mount the directory with the application from the host at the target. Do I
> have to tell gdb where to find some directories?
Sometimes, but it doesn't seem to be the problem here. I think your
binary has had some symbols removed, or something similar. GDB is
looking for "__pthread_threads_events" and not finding it.
Are you running GDB with the file being debugged? Does it have symbol
information? The "in ??" is suspicious.
>
> The application is not stripped. And here is a session log:
>
> (gdb) handle SIG32
> Signal Stop Print Pass to program Description
> SIG32 Yes Yes Yes Real-time event 32
> (gdb) set debug remote 1
> (gdb) target remote 172.16.200.100:2345
> Remote debugging using 172.16.200.100: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: T050b:00000000;0d:10feffbf;0f:10250040;
> Sending packet: $Hg0#df...Ack
> Packet received: OK
> Sending packet: $g#67...Ack
> Packet received:
> 00000000e6feffbf000000000000000000000000000000000000000000000000000000000000
> 000000000000000000000000000010feffbf0000000010250040000000000000000000000000
> 0000000000000000000000000000000000000000000000000000000000000000000000000000
> 0000000000000000000000000000000000000000000000000000000000000000000000000000
> 00000000000000000000000010000000
> Sending packet: $m40002510,4#59...Ack
> Packet received: 0d00a0e1
> Sending packet: $m40002510,4#59...Ack
> Packet received: 0d00a0e1
> Sending packet: $m0,4#fd...Ack
> Packet received: ffffffff
> 0x40002510 in ?? ()
> Sending packet: $m2085340,a8#98...Ack
> Packet received:
> 01000000fc0300000f000000f20c00000c000000dc2c00020d000000e4a50602040000003001
> 0002050000001018000206000000400800020a000000070d00000b0000001000000015000000
> 0000000003000000cc4f080202000000600300001400000011000000170000007c2900021100
> 00007427000212000000080200001300000008000000feffff6f34270002ffffff6f01000000
> f0ffff6f382500020000000000000000
> Sending packet: $qSymbol::#5b...Ack
> Packet received: qSymbol:5f5f707468726561645f746872656164735f6576656e7473
> Packet qSymbol (symbol-lookup) is supported
> Sending packet:
> $qSymbol::5f5f707468726561645f746872656164735f6576656e7473#47...Ack
> Packet received: OK
> (gdb) c
> Continuing.
> Sending packet: $Z0,4000e630,4#d8...Ack
> Packet received:
> Packet Z0 (software-breakpoint) is NOT supported
> Sending packet: $m4000e630,4#8f...Ack
> Packet received: 29e04be2
> Sending packet: $X4000e630,0:#b0...Ack
> Packet received:
> binary downloading NOT suppported by target
> Sending packet: $M4000e630,4:01009fef#d4...Ack
> Packet received: OK
> Sending packet: $Hc0#db...Ack
> Packet received: OK
> Sending packet: $c#63...Ack
> Packet received: T4d0b:3cfbffbf;0d:1cfbffbf;0f:34050440;
>
> Program received signal SIG32, Real-time event 32.
> Sending packet: $g#67...Ack
> Packet received:
> fcffffff080000000000a0bf04ee07021cee070240fbffbf020000005037104060e20a02ac4f
> 0a024ce10f403cfbffbf1cfbffbf1cfbffbf2405044034050440000000000000000000000000
> 0000000000000000000000000000000000000000000000000000000000000000000000000000
> 0000000000000000000000000000000000000000000000000000000000000000000000000000
> 00000000000000000000000010000020
> Sending packet: $m40040534,4#61...Ack
> Packet received: 0040a0e1
> Sending packet: $m40040534,4#61...Ack
> Packet received: 0040a0e1
> Sending packet: $mbffffb3c,4#bf...Ack
> Packet received: 04050440
> Sending packet: $m400404fc,4#c2...Ack
> Packet received: b0a09fe5
> Sending packet: $m40040500,4#5a...Ack
> Packet received: b0209fe5
> Sending packet: $m40040504,4#5e...Ack
> Packet received: 0aa08fe0
> Sending packet: $m40040508,4#62...Ack
> Packet received: 02709ae7
> Sending packet: $m4004050c,4#8d...Ack
> Packet received: 04b04ce2
> Sending packet: $m40040510,4#5b...Ack
> Packet received: 003097e5
> Sending packet: $m40040514,4#5f...Ack
> Packet received: 0050a0e1
> Sending packet: $m40040518,4#63...Ack
> Packet received: 000053e3
> Sending packet: $m4004051c,4#8e...Ack
> Packet received: 1700001a
> Sending packet: $M4000e630,4:29e04be2#d6...Ack
> Packet received: OK
> 0x40040534 in ?? ()
> (gdb)
>
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-17 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 11:29 Frank van Eijkelenburg
2003-01-17 13:54 ` Daniel Jacobowitz
2003-01-17 14:09 ` Frank van Eijkelenburg
2003-01-17 14:14 ` Daniel Jacobowitz
2003-01-17 14:51 ` Frank van Eijkelenburg
2003-01-17 14:56 ` Daniel Jacobowitz
2003-01-17 15:09 ` Frank van Eijkelenburg
2003-01-17 15:17 ` Daniel Jacobowitz [this message]
2003-01-17 15:28 ` Frank van Eijkelenburg
2003-01-17 15:30 ` 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=20030117151701.GA20207@nevyn.them.org \
--to=drow@mvista.com \
--cc=frank.van.eijkelenburg@technolution.nl \
--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