From: Daniel Jacobowitz <drow@false.org>
To: Greg Law <glaw@undo-software.com>
Cc: gdb@sourceware.org
Subject: Re: bfinish writes to random addresses.
Date: Tue, 25 Jul 2006 16:53:00 -0000 [thread overview]
Message-ID: <20060725162821.GB14797@nevyn.them.org> (raw)
In-Reply-To: <44C645C0.1050409@undo-software.com>
On Tue, Jul 25, 2006 at 05:24:32PM +0100, Greg Law wrote:
> >Warning when returning from something with a symbol to something
> >without a symbol is an interesting suggestion. Does anyone else have
> >comments? Should this warn?
> >
> >(gdb) bt
> >#0 foo()
> >#1 0x4000000 in ???
> >(gdb) finish
> >
>
> I was actually suggesting an error rather than a warning. In this case,
> it seems that writing into 0x40000000 is almost certainly not what the
> user wants gdb to be doing.
Surprisingly often it is. We need to be sparing with errors.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-25 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 15:41 Greg Law
2006-07-25 15:42 ` Daniel Jacobowitz
2006-07-25 16:09 ` Greg Law
2006-07-25 16:20 ` Daniel Jacobowitz
2006-07-25 16:27 ` Greg Law
2006-07-25 16:53 ` Daniel Jacobowitz [this message]
2006-07-25 18:40 ` Mark Kettenis
2006-07-26 1:21 ` Daniel Jacobowitz
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=20060725162821.GB14797@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=glaw@undo-software.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