[Bug ld/990] "nm -l" doesn't work well on relocatable files

2005-06-06 Thread george at mvista dot com
--- Additional Comments From george at mvista dot com 2005-06-06 14:49 --- I started this bug because gdb gives wrong source information on some symbols (in the particular case it was/is entry.S in the linux kernel). I also noted that nm seemed to resolve the symbols to the same source

[Bug ld/990] "nm -l" doesn't work well on relocatable files

2005-06-06 Thread hjl at lucon dot org
--- Additional Comments From hjl at lucon dot org 2005-06-06 14:56 --- I checked in my patch. I will have a followup patch later. nm and gdb may or may not share that piece of code. You need to file a gdb bug report. BTW, does entry.S have dwarf debug info? does gdb get wrong line numbe

[Bug ld/990] "nm -l" doesn't work well on relocatable files

2005-06-06 Thread george at mvista dot com
--- Additional Comments From george at mvista dot com 2005-06-06 15:59 --- Subject: Re: "nm -l" doesn't work well on relocatable files hjl at lucon dot org wrote: > --- Additional Comments From hjl at lucon dot org 2005-06-06 14:56 > --- > I checked in my patch. I will have a

[Bug ld/990] "nm -l" doesn't work well on relocatable files

2005-06-06 Thread qunyingpan at yahoo dot com
--- Additional Comments From qunyingpan at yahoo dot com 2005-06-06 16:50 --- Subject: Re: "nm -l" doesn't work well on relocatable files George, so you are debugging an executable (vmlinux), not a relocatable file when you see this problem, right? The problem reported here and the p

[Bug ld/990] "nm -l" doesn't work well on relocatable files

2005-06-06 Thread george at mvista dot com
--- Additional Comments From george at mvista dot com 2005-06-06 17:02 --- Subject: Re: "nm -l" doesn't work well on relocatable files qunyingpan at yahoo dot com wrote: > --- Additional Comments From qunyingpan at yahoo dot com 2005-06-06 > 16:50 --- > Subject: Re: "nm -l"

[Bug ld/990] "nm -l" doesn't work well on relocatable files

2005-06-06 Thread hjl at lucon dot org
--- Additional Comments From hjl at lucon dot org 2005-06-06 17:30 --- If you have a testcase with "nm -l" on executable, I will fix nm. But gdb needs to be fixed separately. -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=990 --- You are receiving this mail because: --

[Bug ld/993] New: fail to link if address of libc function taken in n64

2005-06-06 Thread shay_gal-on at pmc-sierra dot com
The following: #include void (*testme)(void *) = free; int main() { return 0; } Fails with "assertion fail" when trying to link after compiling with -mabi=64. Works fine with o32 or n32. Same issue with taking address of malloc etc... Can take address of non-glibc functions just fine.

[Bug ld/993] fail to link if address of libc function taken in n64

2005-06-06 Thread drow at false dot org
--- Additional Comments From drow at false dot org 2005-06-07 03:33 --- Subject: Re: New: fail to link if address of libc function taken in n64 On Mon, Jun 06, 2005 at 10:00:41PM -, shay_gal-on at pmc-sierra dot com wrote: > Fails with "assertion fail" when trying to link after com