From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22976 invoked by alias); 29 Aug 2005 12:13:03 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 22936 invoked by uid 22791); 29 Aug 2005 12:12:58 -0000 Received: from eth13.com-link.com (HELO real.realitydiluted.com) (208.242.241.164) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 29 Aug 2005 12:12:58 +0000 Received: from localhost ([127.0.0.1]) by real.realitydiluted.com with esmtp (Exim 4.50 #1 (Debian)) id 1E9hZh-0001v1-DC for ; Mon, 29 Aug 2005 06:13:13 -0500 Message-ID: <4312FBC8.1020000@realitydiluted.com> Date: Mon, 29 Aug 2005 12:13:00 -0000 From: "Steven J. Hill" User-Agent: Debian Thunderbird 1.0.6 (X11/20050802) MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Problems with MIPS disassembly and 'rdhwr' instruction... Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-08/txt/msg00106.txt.bz2 Greetings. I am trying to figure out how to get 'rdhwr' instructions to be printed when doing a disassembly in gdb on MIPS binaries. My binaries are not compiled as mips32r2, but as mips1. This is allowable, but it appears that gdb in 'print_insn_mips' will not decoded the 'rdhwr' the instruction because it is a mips1 binary? I have spent a couple of hours trying to figure out the hashing that is done in that function as well as hacking the loop and I have come up with nothing. Can someone help me understand the hashing better and suggest a method/patch to allow me to get the 'rdhwrd' instructions to print instead of the hex opcode? Thanks. -Steve