This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Can back trace be stopped from always prints "char*" strings ?
- From: Paul Koning <Paul_Koning at dell dot com>
- To: drow at false dot org
- Cc: chrisj at rtems dot org, gdb at sourceware dot org
- Date: Wed, 12 Mar 2008 09:59:48 -0400
- Subject: Re: Can back trace be stopped from always prints "char*" strings ?
- References: <47D79ECF.7000900@rtems.org> <20080312123350.GA8997@caradoc.them.org>
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Daniel> 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 ?
Daniel> I don't think there is. You might want to look at "set mem
Daniel> inaccessible-by-default" and the "mem" command; that's good
Daniel> for preventing stray memory reads.
Another possibility: if the embedded target dies when this happens,
that may mean it's getting an addressing error and not handling that.
The target stub should validate addresses it's given and reject any
that are out of range. It also would make sense for it to intercept
any access errors that make it past those range checks and turn them
into error messages back to gdb instead.
paul