Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Jaffer, Bobby" <bobby.jaffer@ngc.com>
To: <gdb@sourceware.org>
Subject: Remote Debugging of a multithreaded application question
Date: Wed, 07 Mar 2007 20:18:00 -0000	[thread overview]
Message-ID: <F6A9F949D87458469D196DDDAA10E2DC06477D1B@xcgca206> (raw)


Question:

I am trying to debug a multithreaded application on a remote linux
machine from a cygwin environment.  I start the gdbserver on the remote
linux machine.  I then run gdb on cygwin and attach to the gdbserver.  I
then can set a break point anywhere in the source code.  But, if I set a
break point in a function that executes outside the main thread, gdb
will not stop at the break point when gdb runs the executable.  And an
error message shows on the gdbserver side.  Specifically, it says "Child
terminated with signal = 5".  The gdbserver then quits at this point.
Why can't gdb debug the other threads in the application?

My setup:   Remote machine is running open suse 10.2 linux.  Windows
machine is running cygwin.

Thanks,

Bobby


             reply	other threads:[~2007-03-07 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 20:18 Jaffer, Bobby [this message]
2007-03-07 20:26 ` 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=F6A9F949D87458469D196DDDAA10E2DC06477D1B@xcgca206 \
    --to=bobby.jaffer@ngc.com \
    --cc=gdb@sourceware.org \
    /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