Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Shaun Jackman <sjackman@gmail.com>, gdb-patches@sourceware.org
Subject: Re: Fix a crash when stepping and unwinding fails
Date: Tue, 21 Feb 2006 10:01:00 -0000	[thread overview]
Message-ID: <ubqx1babp.fsf@gnu.org> (raw)
In-Reply-To: <20060220220331.GA29363@nevyn.them.org> (message from Daniel 	Jacobowitz on Mon, 20 Feb 2006 17:03:31 -0500)

> Date: Mon, 20 Feb 2006 17:03:31 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> Now we'll issue this error instead, and stop stepping:
> 
> Could not step out of the function at 0x80144400 - unwinding failed
> [...]
> Hmm.  Alternatively, we could stop stepping without an error.  Would
> that be better?  Seems likely.  I'll wait for comments before I try
> implementing that, though.  Should we warn when we do that, in addition
> to stopping, or is the warning just noise?

How about making it a warning that depends on "set verbose"?

Btw, I think we should document this message in the manual anyway.


  reply	other threads:[~2006-02-21  4:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21  4:33 Daniel Jacobowitz
2006-02-21 10:01 ` Eli Zaretskii [this message]
2006-02-21 20:28 ` Mark Kettenis
2006-02-21 20:43   ` Daniel Jacobowitz
2006-02-21 20:54     ` Mark Kettenis
2006-02-21 21:03       ` Daniel Jacobowitz
2006-02-21 21:53         ` Mark Kettenis
2006-02-21 22:59           ` Daniel Jacobowitz
2006-02-22 22:00             ` Mark Kettenis
2006-02-23  2:04               ` Daniel Jacobowitz
2006-02-23 17:04                 ` NZG
2006-05-17 17:59               ` Daniel Jacobowitz
2006-06-13 18:42                 ` Daniel Jacobowitz
2006-06-14 12:33                   ` Joel Brobecker
2006-06-16  1:16                     ` Daniel Jacobowitz
2006-02-22  4:28           ` Jim Blandy

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=ubqx1babp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sjackman@gmail.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