Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andrew STUBBS <andrew.stubbs@st.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] keep-variable command
Date: Thu, 17 Nov 2005 19:36:00 -0000	[thread overview]
Message-ID: <20051117192543.GA19824@nevyn.them.org> (raw)
In-Reply-To: <uu0eb5bc5.fsf@gnu.org>

On Thu, Nov 17, 2005 at 09:22:02PM +0200, Eli Zaretskii wrote:
> > Date: Thu, 17 Nov 2005 11:26:07 +0000
> > From: Andrew STUBBS <andrew.stubbs@st.com>
> > Cc: gdb-patches@sources.redhat.com
> > 
> > Currently _all_ convenience variables are deleted when the symbol-file 
> > command is used. The file command also uses symbol-file.
> 
> I think this is a terrible misfeature that we need to fix ASAP,
> regardless of what we do with variables which depend on the symbol
> table.

Lord knows it drives me bonkers.  I didn't know exactly when it
happened (never bothered to look it up).  I seem to recall that you can
also crash GDB a number of different ways with this, which are probably
separate bugs.  This is a bit garbled of a report, I realize; I'm
always neck-deep in something else when it happens...

I have found that GDB will unreliably segfault when I set a watchpoint
using a convenience (or history; are those handled the same way?) variable
and then recompile and rerun the program, causing it to be reloaded.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


      reply	other threads:[~2005-11-17 19:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 15:54 Andrew STUBBS
2005-11-16 20:26 ` Eli Zaretskii
2005-11-17  1:07   ` Jim Blandy
2005-11-17  9:56     ` Daniel Jacobowitz
2005-11-17 15:07       ` Andrew STUBBS
2005-11-17 12:42     ` Andrew STUBBS
2005-11-17 12:26   ` Andrew STUBBS
2005-11-17 19:33     ` Eli Zaretskii
2005-11-17 19:36       ` Daniel Jacobowitz [this message]

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=20051117192543.GA19824@nevyn.them.org \
    --to=drow@false.org \
    --cc=andrew.stubbs@st.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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