From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21808 invoked by alias); 26 Jan 2004 15:56:24 -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 21800 invoked from network); 26 Jan 2004 15:56:23 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 26 Jan 2004 15:56:23 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1Al967-0000nH-DE for ; Mon, 26 Jan 2004 10:56:23 -0500 Date: Mon, 26 Jan 2004 15:56:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: MIPS saved register troubles Message-ID: <20040126155623.GA2979@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i X-SW-Source: 2004-01/txt/msg00302.txt.bz2 I spent some time fiddling with backtraces in an o32 application, using a mips64-linux GDB, this morning. They don't work so well :) The basic problem is the [0,NUM_REGS) hack. mips_register_raw_size reports that register $28 is 8 bytes wide, so legacy_saved_regs_prev_register loads two consecutive saved values into $28, and it looks like 0x7ffffe007ffffd8c ($s8 concatenated with $sp). Fixing this is going to be ugly. Andrew, I don't suppose you have a plan to migrate MIPS to the new frame code, thereby making all this go away? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer