Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Reporting of "program no longer exists"
Date: Sat, 14 Oct 2006 16:33:00 -0000	[thread overview]
Message-ID: <200610142033.16596.ghost@cs.msu.su> (raw)


Hi,
suppose a program being debugged got SIGSEGV and the user for GUI frontend 
tries the "next" command. Here's what happens:

   (gdb) -exec-next
   ^running
   *stopped,reason="signal-received",signal-name="SIGSEGV".....
   (gdb) -exec-next
   ^running
   Couldn't get registers: No such process.
   ^error,msg="Couldn't get registers: No such process."

I think this is a bit unfriendly to frontend.

(1) How can frontend disable the "next" command? Checking for "SIGSEGV" is 
possible, but it a bit of a hack.

(2) After getting the second response, how can frontend understand that this 
is really fatal, unfixable error? Looking at the specific text is obviously a 
hack?

How about making a notion of "inferior state" and announcing changes in the 
state. So, the above would become

   (gdb) -exec-next
   ^running
   *stopped,target-state="noncontinuable",
           reason="signal-received",signal-name="SIGSEGV".....
   (gdb) -exec-next
   ^running
   Couldn't get registers: No such process.
   ^error,msg="Couldn't get registers: No such process.",target-state="dead"

?

- Volodya


             reply	other threads:[~2006-10-14 16:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-14 16:33 Vladimir Prus [this message]
2006-10-14 16:39 ` Daniel Jacobowitz
2006-10-14 20:58   ` Nick Roberts
2006-10-14 21:05     ` Daniel Jacobowitz
2006-10-14 21:17       ` Nick Roberts
2006-10-15  4:36         ` Eli Zaretskii

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=200610142033.16596.ghost@cs.msu.su \
    --to=ghost@cs.msu.su \
    --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