Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: paawan oza <paawan1982@yahoo.com>
Cc: gdb@sourceware.org
Subject: Re: gdb internal error SIGINT/SIGSTOP
Date: Mon, 02 Feb 2009 15:05:00 -0000	[thread overview]
Message-ID: <20090202150506.GB11602@caradoc.them.org> (raw)
In-Reply-To: <735532.80747.qm@web36208.mail.mud.yahoo.com>

On Mon, Feb 02, 2009 at 06:47:02AM -0800, paawan oza wrote:
> Hello,
> 
> I have been modifying gdb for past couple of months.
> I am trying to keep process always running and user should be able to type commands.

Please look at the non-stop debuging which is supported in HEAD.
You will have to change a lot of the same things that non-stop did.

> when I have breakpoints on threads....
> and if main/CLONEs thread is stopped due to breakpoint and if I send 
> SIGINT/SIGSTOP to the main thread....
> eventually I end up getting interrnal gdb assertion error.
> gdb_assert (pid == GET_LWP (lp->ptid));

Sorry, there is no way for us to know the answer to this question
since you have made extensive changes to your GDB.


-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-02-02 15:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 14:47 paawan oza
2009-02-02 15:05 ` Daniel Jacobowitz [this message]
2009-02-02 15:20   ` paawan oza
2009-02-02 15:52     ` Daniel Jacobowitz
2009-02-03  3:05 ` teawater
     [not found]   ` <171515.38221.qm@web36204.mail.mud.yahoo.com>
2009-02-05  8:24     ` teawater
2009-02-05 13:48       ` paawan oza
2009-02-05 15:52         ` teawater
2009-02-05 16:22           ` paawan oza
2009-02-06  5:16             ` teawater
2009-02-06  7:54               ` paawan oza

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=20090202150506.GB11602@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=paawan1982@yahoo.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