From: "Rick Bauer" <rbauer@amnis.com>
To: <insight@sources.redhat.com>
Subject: debugging threads on remote target with insight on cygwin
Date: Wed, 27 Jul 2005 18:01:00 -0000 [thread overview]
Message-ID: <A2B913284A70DD48A71D89C460BBCBF930F4E6@amnis2.amnis.com> (raw)
I've built insight 6.3 on cygwin configured for debugging a remote embedded linux target ( based on RedHat 9.0 ): the target is i686-pc-linux-gnu. I also built the corresponding gdbserver to run on that target. I then use that gdbserver on the target to launch our embedded application. The embedded application is built using cygwin with a cross gcc (i686-pc-linux-gnu ) that compiles and links against a copy of the RedHat 9.0 include directories and runtime libraries . The embedded application uses the pthreads library for threading.
Insight loads the program file and its symbols and connects to the target gdbserver successfully. I can control the execution of the remote application successfully, set breakpoints, single step the application, and view program variables. However "info threads" only shows one thread running on the target whereas multiple threads are actually running. If I set a breakpoint in a routine that is subsequently invoked from a newly created thread, gdbserver quits with a message "killing inferior", and insight displays a message indicating "Program terminated with signal SIGTRAP, Trace/breakpoint trap". It appears that either gdbserver or insight is unable to handle a breakpoint in a routine that is invoked when a new thread begins to run in the embedded application. When I built the gdbserver, the messages output from the build seemed to indicate that it had included support for threads ( thread_db ). I'm not as sure about insight. The same problem occurs if I try debugging the application remotely with the gdb command line rather than with insight. I also have the same problem with insight 6.1.
Does insight on cygwin support threads on the remote target if that target is an embedded RedHat Linux? I configured insight with the following command, "configure --target=i686-pc-linux-gnu". Do I need to configure or make insight in a different way to enable support for threads?
next reply other threads:[~2005-07-27 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 18:01 Rick Bauer [this message]
2005-08-01 18:49 ` Keith Seitz
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=A2B913284A70DD48A71D89C460BBCBF930F4E6@amnis2.amnis.com \
--to=rbauer@amnis.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).