Program no longest exists?

Program no longest exists?

[Alvin Beach]

Hello all,

I have recently upgraded from suse 9.1 to suse 9.3. Since upgrading, I can no 
longer debug programs that I was able to debug before.

When I run gdb, the program runs fine as long there are no breakpoints. As 
soon as I set a breakpoint and run the program, I get message:

	Program terminated with signal SIGTRAP, Trace/breakpoint trap.
        Program no longer exists.

Sometimes it happens right away, sometime after I step over the breakpoint.

I have found reference from googling that this may be pthread related? My 
programs do use pthread.

Is there a work-around or fix for this. Without gdb, my programs are no 
littered with cerr/printf statements.

Thanks,

Alvin

-- 
Please reply to the mailing list.

Re: Program no longest exists?

[Daniel Jacobowitz]

On Mon, Jun 06, 2005 at 10:16:47AM -0300, Alvin Beach wrote:
> Hello all,
> 
> I have recently upgraded from suse 9.1 to suse 9.3. Since upgrading, I can no 
> longer debug programs that I was able to debug before.
> 
> When I run gdb, the program runs fine as long there are no breakpoints. As 
> soon as I set a breakpoint and run the program, I get message:
> 
> 	Program terminated with signal SIGTRAP, Trace/breakpoint trap.
>         Program no longer exists.
> 
> Sometimes it happens right away, sometime after I step over the breakpoint.
> 
> I have found reference from googling that this may be pthread related? My 
> programs do use pthread.
> 
> Is there a work-around or fix for this. Without gdb, my programs are no 
> littered with cerr/printf statements.

This is usually a bug in your kernel; maybe SuSE has an update kernel
available.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: Program no longest exists?

[Alvin Beach]

On Monday 06 June 2005 10:21, Daniel Jacobowitz wrote:
> On Mon, Jun 06, 2005 at 10:16:47AM -0300, Alvin Beach wrote:
> > Hello all,
> >
> > I have recently upgraded from suse 9.1 to suse 9.3. Since upgrading, I
> > can no longer debug programs that I was able to debug before.
> >
> > When I run gdb, the program runs fine as long there are no breakpoints.
> > As soon as I set a breakpoint and run the program, I get message:
> >
> > 	Program terminated with signal SIGTRAP, Trace/breakpoint trap.
> >         Program no longer exists.
> >
> > Sometimes it happens right away, sometime after I step over the
> > breakpoint.
> >
> > I have found reference from googling that this may be pthread related? My
> > programs do use pthread.
> >
> > Is there a work-around or fix for this. Without gdb, my programs are no
> > littered with cerr/printf statements.
>
> This is usually a bug in your kernel; maybe SuSE has an update kernel
> available.

Unfortunately, they don't. I guess I will just have to wait until they do. In 
the meantime, I'm going to look for a way to dump a stack trace (like in KDE 
when an app crashes - which is happening a lot for me). 

Thanks for the info.

Alvin

-- 
Please reply to the mailing list.