From: Daniel Jacobowitz <drow@false.org>
To: Chris Johns <chrisj@rtems.org>
Cc: gdb@sourceware.org
Subject: Re: Can back trace be stopped from always prints "char*" strings ?
Date: Wed, 12 Mar 2008 14:00:00 -0000 [thread overview]
Message-ID: <20080312123350.GA8997@caradoc.them.org> (raw)
In-Reply-To: <47D79ECF.7000900@rtems.org>
On Wed, Mar 12, 2008 at 08:13:51PM +1100, Chris Johns wrote:
> Is there a way to stop the bt accessing the char* data and just printing
> the pointer value ?
I don't think there is. You might want to look at "set mem
inaccessible-by-default" and the "mem" command; that's good for
preventing stray memory reads.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-03-12 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 11:50 Chris Johns
2008-03-12 14:00 ` Daniel Jacobowitz [this message]
2008-03-12 14:23 ` Paul Koning
2008-03-13 18:13 ` Chris Johns
2008-03-12 15:05 ` Thiago Jung Bauermann
2008-03-12 20:15 ` Michael Snyder
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=20080312123350.GA8997@caradoc.them.org \
--to=drow@false.org \
--cc=chrisj@rtems.org \
--cc=gdb@sourceware.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