From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16124 invoked by alias); 28 Apr 2006 18:20:36 -0000 Received: (qmail 16110 invoked by uid 22791); 28 Apr 2006 18:20:34 -0000 X-Spam-Check-By: sourceware.org Received: from mail-out4.apple.com (HELO mail-out4.apple.com) (17.254.13.23) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 28 Apr 2006 18:20:29 +0000 Received: from relay8.apple.com (a17-128-113-38.apple.com [17.128.113.38]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id k3SIKQdF010557; Fri, 28 Apr 2006 11:20:26 -0700 (PDT) Received: from [17.219.198.216] (unknown [17.219.198.216]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by relay8.apple.com (Apple SCV relay) with ESMTP id E199F4CC; Fri, 28 Apr 2006 11:20:25 -0700 (PDT) In-Reply-To: <20060428181432.GK4579@networkno.de> References: <20060428123353.GF4579@networkno.de> <0C690A4E-C9EC-4BBF-AD0E-395C77D6BD15@apple.com> <20060428181432.GK4579@networkno.de> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Cc: binutils@sourceware.org Content-Transfer-Encoding: 7bit From: Eric Christopher Subject: Re: [PATCH] Force mips16 disassembled addresses to odd values Date: Fri, 28 Apr 2006 20:36:00 -0000 To: Thiemo Seufer X-Mailer: Apple Mail (2.749.3) X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2006-04/txt/msg00419.txt.bz2 On Apr 28, 2006, at 11:14 AM, Thiemo Seufer wrote: > Eric Christopher wrote: >> >> On Apr 28, 2006, at 5:33 AM, Thiemo Seufer wrote: >> >>> Hello All, >>> >>> this patch forces some disassembled mips16 addresses to odd values, >>> this helps gdb to handle mips16 code better. >> >> Uh. What on earth? Could you explain this one? :) > > Gdb has to find out what part is MIPS16 in mixed MIPS32/MIPS16 code > binaries. The code is used in MIPS' SDE6 toolchain, I don't know if > there are better ways like relying on DWARF info (in a detached file > for raw binaries?). Good question. What's done for arm/thumb? -eric