Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: David Lecomber <david@streamline-computing.com>
Cc: drow@false.org,
	"gdb-patches@sources.redhat.com"
	<1101033470.22991.41.camel@cpc2-oxfd5-5-0-cust91.oxfd.cable.ntl.com>
	(message from David Lecomber on Sun, 21 Nov 2004 10:37:50 +0000)
Subject: Re: [PATCH] Seg fault whilst stepping when watch set [ping!] [in breakpoint.c]
Date: Sun, 21 Nov 2004 19:40:00 -0000	[thread overview]
Message-ID: <01c4d001$Blat.v2.2.2$ab4fe0a0@zahav.net.il> (raw)
In-Reply-To: <20041121064940.GB909@nevyn.them.org>

> From: David Lecomber <david@streamline-computing.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, patches <gdb-patches@sources.redhat.com>
> Date: Sun, 21 Nov 2004 10:37:50 +0000
> 
> 
> > > > (gdb) watch i
> > > > During symbol reading, incomplete CFI data; unspecified registers (e.g.,
> > > > eax) at 0x804bc35.
> > 
> > I think this should be fixed in HEAD, as of now; if not, we'll have to
> > look at it again.  Andrew checked in a patch for this recently.
> 
> Still happens with a fresh CVS from one minute ago..

Btw, I must say that this message is utterly unhelpful to users who,
like myself, are not DWARF-2 gurus: it sounds grave and scary, and yet
conveys no information whatsoever about user-level implications of the
problem, to say nothing about any possible ways to work around it.

In other words, this message should be a textbook example of how _not_
to design user interfaces.

Can we please replace the message text with something more useful and
slightly more self-explanatory?


  parent reply	other threads:[~2004-11-21 19:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <01c4cef8$Blat.v2.2.2$3fd12960@zahav.net.il>
2004-11-21  0:24 ` David Lecomber
2004-11-21  0:42   ` Daniel Jacobowitz
2004-11-21  5:29     ` Eli Zaretskii
2004-11-21  6:48       ` Daniel Jacobowitz
2004-11-21  5:19   ` Eli Zaretskii
2004-11-21  6:49     ` Daniel Jacobowitz
2004-11-21 10:36       ` David Lecomber
2004-11-21 19:40       ` Eli Zaretskii [this message]
2004-10-17  0:09 [PATCH] Seg fault whilst stepping when watch set David Lecomber
2004-10-25 16:10 ` [PATCH] Seg fault whilst stepping when watch set [ping!] David Lecomber
2004-11-01 22:05   ` [PATCH] Seg fault whilst stepping when watch set [ping!] [in breakpoint.c] David Lecomber
2004-11-02  4:38   ` Eli Zaretskii
     [not found]     ` <1099385491.31287.19.camel@cpc1-oxfd5-5-0-cust86.oxfd.cable.ntl.com>
2004-11-02 21:40       ` Eli Zaretskii
2004-11-03 12:08         ` David Lecomber
2004-11-17 21:38           ` David Lecomber
2004-11-03 18:09         ` 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='01c4d001$Blat.v2.2.2$ab4fe0a0@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=1101033470.22991.41.camel@cpc2-oxfd5-5-0-cust91.oxfd.cable.ntl.com \
    --cc=david@streamline-computing.com \
    --cc=drow@false.org \
    /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