Re: gdb internal error SIGINT/SIGSTOP

[paawan oza <paawan1982 at yahoo dot com>]

Hello,

I completely understand, and I appreciate what you have said.
but is it possible to answer following ?

1) in what all situation
gdb_assert (pid == GET_LWP (lp->ptid)) could come
(I am using gdb-6.7)
I do not expect too much technical internal details of gdb here...
but at an abstract level, if it is possible to explain.

2) I would like to contribute in open source for reversible debugging.
but I am not getting any clue how I can start and where to go ahead ?
would you please guide me ?

Regards,
..Paawan.



--- On Mon, 2/2/09, Daniel Jacobowitz <drow@false.org> wrote:

> From: Daniel Jacobowitz <drow@false.org>
> Subject: Re: gdb internal error SIGINT/SIGSTOP
> To: "paawan oza" <paawan1982@yahoo.com>
> Cc: gdb@sourceware.org
> Date: Monday, February 2, 2009, 8:35 PM
> 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