Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Frédéric Riss" <frederic.riss@gmail.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Denis PILAT <denis.pilat@st.com>, Vladimir Prus <ghost@cs.msu.su>,
	 gdb-patches@sources.redhat.com
Subject: Re: [RFC] varobj deletion after the binary has changed
Date: Wed, 24 Jan 2007 22:08:00 -0000	[thread overview]
Message-ID: <1169676493.5160.14.camel@funkylaptop> (raw)
In-Reply-To: <17847.54349.654238.452957@kahikatea.snap.net.nz>

Le jeudi 25 janvier 2007 à 10:49 +1300, Nick Roberts a écrit :
>  > > And what kind of problems does it cause, for the record? I'd expect that
>  > > attempt of evaluating such expressions will result in value being "",
>  > > and in_scope="false". Do you get anything worse than that?
> 
> It's a global variable so I don't think it will ever be reported as out
> of scope.
> 
>  > Yes we are, gdb crashes.
> 
> This is a bug in GDB and how to deal with variable objects when restarting
> should be a separate issue.  I see the same problem in a CVS snapshot of
> 6.2 vintage but not in GDB 6.3 from Fedora Core 5.  So unless the problem
> disappeared in 6.3 and reasppeared later, which is unlikely, I think Fedora
> must have solved it with one of their patches.  The problem is I don't know
> which one.

Just a shot in the dark: did you test with a memory checker like
valgrind? The fact that there's no crash doesn't mean that there's no
buggy memory access.

Fred.


  parent reply	other threads:[~2007-01-24 22:08 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 12:32 Denis PILAT
2007-01-23 12:45 ` Daniel Jacobowitz
2007-01-23 12:52   ` Vladimir Prus
2007-01-23 14:49     ` Denis PILAT
2007-01-24 21:49       ` Nick Roberts
2007-01-24 22:07         ` Daniel Jacobowitz
2007-01-24 22:08         ` Frédéric Riss [this message]
2007-01-24 22:18           ` Nick Roberts
2007-01-24 22:52             ` Frédéric Riss
2007-01-24 23:14               ` Nick Roberts
2007-01-25  2:41             ` Daniel Jacobowitz
2007-01-25 20:50               ` Nick Roberts
2007-01-26  7:25                 ` Denis PILAT
2007-01-23 17:20   ` Denis PILAT
2007-01-25 17:28     ` Denis PILAT
2007-01-25 22:31       ` Nick Roberts
2007-01-25 23:27         ` Daniel Jacobowitz
2007-01-29 12:39           ` Denis PILAT
2007-01-29 22:12             ` Nick Roberts
2007-01-30  8:49               ` Denis PILAT
2007-01-31 19:07               ` Denis PILAT
2007-01-31 21:29                 ` Nick Roberts
2007-02-01  9:49                   ` Denis PILAT
2007-02-08 16:41                     ` Daniel Jacobowitz
2007-02-08 19:33                       ` Nick Roberts
2007-02-08 19:55                         ` Daniel Jacobowitz
2007-02-09 15:43                         ` Eli Zaretskii
2007-02-12 21:10                           ` Denis PILAT
2007-02-13  0:11                             ` Nick Roberts
2007-02-13  8:26                               ` Denis PILAT
2007-02-20 16:06                             ` Andreas Schwab
2007-02-20 16:17                               ` Denis PILAT

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=1169676493.5160.14.camel@funkylaptop \
    --to=frederic.riss@gmail.com \
    --cc=denis.pilat@st.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    --cc=nickrob@snap.net.nz \
    /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