From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-32825-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 15038 invoked by alias); 14 Aug 2008 15:03:43 -0000
Received: (qmail 14998 invoked by uid 22791); 14 Aug 2008 15:03:36 -0000
X-Spam-Check-By: sourceware.org
Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 14 Aug 2008 15:02:52 +0000
Received: from nan.false.org (localhost [127.0.0.1]) 	by nan.false.org (Postfix) with ESMTP id DB5E1983B4; 	Thu, 14 Aug 2008 15:02:50 +0000 (GMT)
Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) 	by nan.false.org (Postfix) with ESMTP id C5E8598243; 	Thu, 14 Aug 2008 15:02:50 +0000 (GMT)
Received: from drow by caradoc.them.org with local (Exim 4.69) 	(envelope-from <drow@caradoc.them.org>) 	id 1KTeLh-0001yx-F4; Thu, 14 Aug 2008 11:02:49 -0400
Date: Thu, 14 Aug 2008 20:30:00 -0000
From: Daniel Jacobowitz <drow@false.org>
To: Andr? P?nitz <apoenitz@trolltech.com>
Cc: gdb@sourceware.org
Subject: Re: How to interpret (encoded?) gdb response
Message-ID: <20080814150249.GA7601@caradoc.them.org>
Mail-Followup-To: Andr? P?nitz <apoenitz@trolltech.com>, gdb@sourceware.org
References: <200808141113.21141.apoenitz@trolltech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200808141113.21141.apoenitz@trolltech.com>
User-Agent: Mutt/1.5.17 (2008-05-11)
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-08/txt/msg00178.txt.bz2

On Thu, Aug 14, 2008 at 11:13:08AM +0200, Andr? P?nitz wrote:
> 
> Hi all.
> 
> I do the foillowing:
> 
>   - run an inferior containing a tight endless loop
>   - attach to it with gdb -pid=<id>
>   - run  'kill <pid>' in shell
>   - do  -exec-continue
> 
> then I get:
> 
>   67^running
>   (gdb) 
>   &"Cannot access memory at address 0x7fff6ca72a4c\n"
>   &"\240\240\354\003\n"
>   67^error,msg="\240\240\354\003"
> 
> Does that msg have any meaning, i.e. how would I "decode" it?
> The message appears also in a non-MI environment, but is even
> less legible there...

No, it's some sort of bug or bad pointer.  Does this happen in HEAD?

-- 
Daniel Jacobowitz
CodeSourcery