From: "Frank van Eijkelenburg" <frank.van.eijkelenburg@technolution.nl>
To: "Gnu Debugger mailing list" <gdb@sources.redhat.com>
Subject: multithreaded remote debugging
Date: Fri, 17 Jan 2003 11:29:00 -0000 [thread overview]
Message-ID: <JJEILELDMJJENLCGJHOIGEDHCEAA.frank.van.eijkelenburg@technolution.nl> (raw)
Hi, I'm new to gdb. I try to remote debug an application:
I have a linux machine with redhat installed (2.4.7-10), this is the host.
On the target an ARM processor is running with linux kernel 2.4.16. I
compiled gdb on the host (with target arm-linux). I also cross-compiled
gdbserver. My application (which I want to debug) is compiled with compiler
option -g. I can start the gdbserver on the target and gdb on the host and
have a connection by tcp/ip. The application is multithreaded and uses the
libpthread library. If I ignore the SIG32 signal (with "handle SIG32 nostop"
and "handle SIG32 noprint") I can run the application. However, if I try to
execute "info threads" I only get information about one thread (the main
thread??). I can put breakpoints in the main thread and step through the
code, but if I put a breakpoint in another thread, the debugger will stop,
but I cannot step through the code:
Program received signal SIGTRAP, Trace/breakpoint trap.
0x400ab2e4 in ?? ()
(gdb) n
Cannot find bounds of current function
What do I wrong or is it not possible to step through the code of other
threads beside the main thread?
TIA
Frank van Eijkelenburg
System Designer
--------------------------------------------------------------------------
Technolution B.V.
Telephone: +31(0)182 59 40 00
Fax: +31(0)182 53 97 36
E-mail:
frank.van.eijkelenburg@technolution.nl
Visit us at:
www.technolution.nl
Mailing address:
P.O. Box 2013 - 2800 BD Gouda - The Netherlands
Address:
Zuidelijk Halfrond 1 - 2801 DD Gouda - The Netherlands
GPS:
N 52º.00'58,2 O 4º.41'05,2Â
--------------------------------------------------------------------------
This e-mail is intended exclusively for the addressee(s), and may not
be passed on to, or made available for use by any person other than the
addressee(s). Technolution B.V. rules out any and every liability resulting
from any electronic transmission.
next reply other threads:[~2003-01-17 11:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 11:29 Frank van Eijkelenburg [this message]
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
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=JJEILELDMJJENLCGJHOIGEDHCEAA.frank.van.eijkelenburg@technolution.nl \
--to=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