From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22093 invoked by alias); 12 Mar 2008 14:00:19 -0000 Received: (qmail 22081 invoked by uid 22791); 12 Mar 2008 14:00:18 -0000 X-Spam-Check-By: sourceware.org Received: from aussmtpmrkps320.us.dell.com (HELO aussmtpmrkps320.us.dell.com) (143.166.224.254) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 12 Mar 2008 13:59:52 +0000 X-IronPort-AV: E=Sophos;i="4.25,488,1199685600"; d="scan'208";a="349716893" Received: from unknown (HELO M31.equallogic.com) ([12.110.134.31]) by aussmtpmrkps320.us.dell.com with SMTP; 12 Mar 2008 08:59:50 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18391.57812.944766.963990@gargle.gargle.HOWL> Date: Wed, 12 Mar 2008 14:23:00 -0000 From: Paul Koning To: drow@false.org Cc: chrisj@rtems.org, gdb@sourceware.org Subject: Re: Can back trace be stopped from always prints "char*" strings ? References: <47D79ECF.7000900@rtems.org> <20080312123350.GA8997@caradoc.them.org> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid 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/msg00129.txt.bz2 >>>>> "Daniel" == Daniel Jacobowitz 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