From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Received: (qmail 4050 invoked from network); 3 Feb 2002 15:57:28 -0000 Received: from unknown (HELO mail.sandvine.com) (209.167.74.226) by sources.redhat.com with SMTP; 3 Feb 2002 15:57:28 -0000 Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Sun, 3 Feb 2002 10:57:21 -0500 Message-ID: From: Don Bowman To: 'Daniel Jacobowitz ' , Don Bowman Cc: ''Stan Shebs' ' , ''Greg McGary' ' , "'gdb@sources.redhat.com '" , "'echristo@redhat.com '" Subject: RE: MIPS stack tracing Date: Sun, 03 Feb 2002 12:29:00 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-SW-Source: 2002-02/txt/msg00063.txt.bz2 Daniel Jacobowitz wrote: >Most of what it needs should be in .pdr, which is available regardless >of -g. I don't believe heuristics should be necessary in that case. >The logic is a bit twisted, though... Has anyone checked out this older message from the mailing list? Re: Questions about GCC MIPS R5900's mdebug section http://sources.redhat.com/ml/gdb/1999-q4/msg00290.html I indeed have no .mdebug section, and I indeed see an unsuccessful search for "__GDB_EFI_INFO__". I do have a .pdr section. On the surface this would seem to be my problem. Should this sym lookup be prefaced with a check for a .mdebug section? Also, from scanning the sources, I would have to guess that the alpha architecture is suffering the same problem.