This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/216: add-symbol-file problem with snapshot 20010919
- To: gdb-gnats at sources dot redhat dot com
- Subject: gdb/216: add-symbol-file problem with snapshot 20010919
- From: renwei at huawei dot com
- Date: 27 Sep 2001 01:38:09 -0000
- Reply-To: renwei at huawei dot com
>Number: 216
>Category: gdb
>Synopsis: add-symbol-file problem with snapshot 20010919
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Sep 26 18:48:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: HUAWEI TECH
>Release: snapshot 20010919
>Organization:
>Environment:
host i386 box( pIII ), target mipsel.
>Description:
1. compile the cross gdb target mipsel , host i386.
2. get a module .o file of mipsel, have 3 functions.
3. run gdb.
4. use command "add-symbol-file hello.o 0x10000000"
5. confirm yes.
6. use command "print my_func1" "print my_func2" "print my_func3"
7. all show the SAME address 0x10000000.
*** we meet this proble when we want to use kgdb to debug some module on mipsel board, because of this , we can't debug the module funtions, but the kernel functions seems
all right.
the module file is attached.
>How-To-Repeat:
every time .
1. compile the cross gdb target mipsel , host i386.
2. get a module .o file of mipsel, have 3 functions.
3. run gdb.
4. use command "add-symbol-file hello.o 0x10000000"
5. confirm yes.
6. use command "print my_func1" "print my_func2" "print my_func3"
7. all show the SAME address 0x10000000.
>Fix:
I try to trace down the gdb,
it seems to read the elf symbol correctly,
the i386 native gdb doesn't have this problem.
>Release-Note:
>Audit-Trail:
>Unformatted: