From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8450 invoked by alias); 12 Mar 2008 14:23:40 -0000 Received: (qmail 8437 invoked by uid 22791); 12 Mar 2008 14:23:40 -0000 X-Spam-Check-By: sourceware.org Received: from igw2.br.ibm.com (HELO igw2.br.ibm.com) (32.104.18.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 12 Mar 2008 14:23:06 +0000 Received: from mailhub3.br.ibm.com (mailhub3 [9.18.232.110]) by igw2.br.ibm.com (Postfix) with ESMTP id A979917F54F for ; Wed, 12 Mar 2008 11:14:54 -0300 (BRST) Received: from d24av01.br.ibm.com (d24av01.br.ibm.com [9.18.232.46]) by mailhub3.br.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m2CEMqGI3633400 for ; Wed, 12 Mar 2008 11:22:55 -0300 Received: from d24av01.br.ibm.com (loopback [127.0.0.1]) by d24av01.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m2CEMpbP030459 for ; Wed, 12 Mar 2008 11:22:52 -0300 Received: from [9.18.238.95] (dyn531828.br.ibm.com [9.18.238.95]) by d24av01.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m2CEMpux030424; Wed, 12 Mar 2008 11:22:51 -0300 Subject: Re: Can back trace be stopped from always prints "char*" strings ? From: Thiago Jung Bauermann To: Daniel Jacobowitz Cc: Chris Johns , gdb@sourceware.org In-Reply-To: <20080312123350.GA8997@caradoc.them.org> References: <47D79ECF.7000900@rtems.org> <20080312123350.GA8997@caradoc.them.org> Content-Type: text/plain Date: Wed, 12 Mar 2008 15:05:00 -0000 Message-Id: <1205331771.6643.35.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-03/txt/msg00130.txt.bz2 On Wed, 2008-03-12 at 08:33 -0400, Daniel Jacobowitz wrote: > 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. I think the newly introduced "set print frame-arguments" would help here. It went in after GDB 6.7 though. -- []'s Thiago Jung Bauermann Software Engineer IBM Linux Technology Center