From: Daniel Jacobowitz <drow@false.org>
To: Robert Norton <rnorton@broadcom.com>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: Re: (Another) Segfault in varobj.c
Date: Wed, 08 Aug 2007 18:09:00 -0000 [thread overview]
Message-ID: <20070808180930.GA12779@caradoc.them.org> (raw)
In-Reply-To: <B0D822BFECD50F4991F2516EA50F273C021AC1E6@NT-IRVA-0752.brcm.ad.broadcom.com>
On Wed, Aug 08, 2007 at 10:59:56AM -0700, Robert Norton wrote:
> I also had a problem with one of the tests: mi-var-cmd.exp creates a
> varobj from a char* but due to gdb interpreting it is a null terminated
> string it appears to be modified even though it is actually the llong
> variable which is allocated after it in memory which has changed. What's
> needed is some way to tell gdb that lpcharacter really is just a char *
> (not a pointer to a null terminated string).
Or not to treat it as a string (I have some posted work in that area)
or just to NUL terminate it...
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-08-08 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 11:49 Robert Norton
2007-08-07 12:13 ` Nick Roberts
2007-08-07 15:08 ` Vladimir Prus
2007-08-07 16:12 ` Robert Norton
2007-08-08 18:01 ` Robert Norton
2007-08-08 18:09 ` 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=20070808180930.GA12779@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=rnorton@broadcom.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