No line number info on GDB 7.0 using remote stub.

higepon higepon@gmail.com
Wed Dec 30 08:25:00 GMT 2009


Hi.

After a long struggle, I found gdb-6.3-2.exe for Mingw shows line number.
I run gdb-6.3.2.exe with wine on Linux.

So this problem may be caused from
(1) Changes between GDB 6.3 and 7.0.

or

(2) My miss configure of GDB 7.0


Thank you.

On Wed, Dec 23, 2009 at 10:38 PM, higepon <higepon@gmail.com> wrote:
> Hi.
> I'm trying remote debug using i386-stub.c on my OS.
> GDB stub seems to work for remote debug, but it doesn't show souce
> code line number.
> Will you please teach me why it doesn't or how to know what is wrong with it?
>
> [1] GDB I use.
> - gdb-7.0
> - ./configure --prefix=~/tmp/ --target=i586-mingw32msvc
>
> [2] commands I issued
> % ~/tmp/bin/i586-mingw32msvc-gdb test/monapi/mutex/TMUTEX.EXE
> (gdb) target remote localhost:43770
> Remote debugging using localhost:43770
> Ignoring packet error, continuing...
> warning: unrecognized item "timeout" in "qSupported" response
> 0xa00013bc in testClassMutex() ()
>
> The pc(eip) address 0xa00013bc is correct, but without souce code line number.
>
> [3] things I tried
> - compile with -g flag
> - maint print symbols symbols.txt /home/taro/mona/test/monapi/mutex/mutex.cpp
>  -- symbols.txt is empty.
> - check source code information with objdjump
>  -- objdump shows correct source line number as follows.
>
> % /usr/bin/i586-mingw32msvc-objdump -lS test/monapi/mutex/TMUTEX.EXE|less
> ...
>
> void testClassMutex()
> {
>    mutex = new Mutex();
> a00013b6:       89 1d 08 40 00 a0       mov    %ebx,0xa0004008
> /home/taro/mona/test/monapi/mutex/mutex.cpp:132
>    ASSERT_TRUE(mutex != NULL);
>
>    uintptr_t* p = (uintptr_t*)0;
>    *p = 1;
> a00013bc:       c7 05 00 00 00 00 01    movl   $0x1,0x0
> a00013c3:       00 00 00
> /home/taro/mona/test/monapi/mutex/mutex.cpp:129
> }
>
> ...
>
> If I did something wrong, I appreciate your pointing me out.
> Cheers.
> ---
> Taro Minowa(Higepon)
>
> http://www.monaos.org/
> http://code.google.com/p/mosh-scheme/
>



More information about the Gdb mailing list