Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Alvin Beach <abeach@deepvision.ca>
To: gdb@sources.redhat.com
Subject: Program no longest exists?
Date: Mon, 06 Jun 2005 13:15:00 -0000	[thread overview]
Message-ID: <200506061016.47931.abeach@deepvision.ca> (raw)

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.


             reply	other threads:[~2005-06-06 13:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-06 13:15 Alvin Beach [this message]
2005-06-06 13:46 ` Daniel Jacobowitz
2005-06-06 13:32   ` Alvin Beach

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=200506061016.47931.abeach@deepvision.ca \
    --to=abeach@deepvision.ca \
    --cc=gdb@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