This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
gdb/2193: MIPS-32 fails to show correct function arguments with stabs+
- From: hans at ellips dot nl
- To: gdb-gnats at sources dot redhat dot com
- Date: 26 Oct 2006 13:54:53 -0000
- Subject: gdb/2193: MIPS-32 fails to show correct function arguments with stabs+
- Reply-to: hans at ellips dot nl
>Number: 2193
>Category: gdb
>Synopsis: MIPS-32 fails to show correct function arguments with stabs+
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Thu Oct 26 13:58:01 UTC 2006
>Closed-Date:
>Last-Modified:
>Originator: hans@ellips.nl
>Release: GDB 6.5
>Organization:
>Environment:
CYGWIN_NT-5.1 xpws-hans 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin
GCC:
Target: mips-elf
Configured with: ../gcc-4.1.1/configure --prefix=/usr/local/gcc-4.1.1-mips-elf -
-target=mips-elf --with-gnu-as --with-gnu-ld --with-newlib --with-headers=/gcc/n
ewlib-1.14.0/newlib/libc/include --enable-languages=c,c++ --disable-shared --dis
able-libssp
Thread model: single
gcc version 4.1.1
>Description:
When you step into a function like
int func(int arg)
{
...
}
GDB shows the wrong value for arg. When the argument is on the stack at location 34, GDB takes the value at location 68. So it looks like it thinks the arguments are stored in 64 bit or something. Any other debug format like dwarf-2 shows arg correctly, but has more difficulties in finding the stack frame. Stabs+ looks like the most stable format but has this bug in it.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: