Re: Can back trace be stopped from always prints "char*" strings ?

[Chris Johns <chrisj@rtems.org>]

Paul Koning wrote:
>>>>>> "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.
> 

This is working so I am able to move forward. Thanks. I wonder if it is such a 
good idea for GDB to display the string a char* points to by default when 
handling a union.

> 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.

This may work for a stub running on the target. I have a gdbserver talking 
over USB to a BDM pod connected to a Coldfire. The gdbserver knows nothing 
about the target memory map and I am not sure it should need to know. I think 
the mem command is a good idea. Thank for the idea.

Regards
Chris