This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: BFD causes a SIGSEGV
- From: "Bloch, Jack" <Jack dot Bloch at icn dot siemens dot com>
- To: "'gdb at sources dot redhat dot com'" <gdb at sources dot redhat dot com>
- Date: Thu, 8 Jul 2004 12:07:23 -0700
- Subject: RE: BFD causes a SIGSEGV
As a follow up, I have compared the utility running under a 2.4 Kernel with
the same utility running under a 2.6 Kernel. It seems that the section->vma
is not seen. i.e. only the offset of the symbol itself is seen. Why is this
different under 2.6? Is this a gcc/linker issue.
Jack Bloch
Siemens ICN
phone (561) 923-6550
e-mail jack.bloch@icn.siemens.com
-----Original Message-----
From: Bloch, Jack
Sent: Thursday, July 08, 2004 8:16 AM
To: gdb@sources.redhat.com
Subject: BFD causes a SIGSEGV
I have a utility that was built under a 2.4 Kernel. I am now running a stock
2.6.5 Kernel from SuSE and my utility causes a SEGV. The problem is with the
BFD utility. I have the following line of code.
p_sym->value = bfd_asymbol_value(i_sym);
In looking at the macro definition in bfd.h, I see that this used
i_sym->base. The value in here is 0x190. The defintion of bfd_asymbol_value
did not change between my 2.4 and 2.6 Kernel.
Perhaps this is not the correct mailing list for this problem, but has
anyone seen similar problems using the BFD under 2.6.
I have version 2.15.90 of libbfd.
Jack Bloch
Siemens ICN
phone (561) 923-6550
e-mail jack.bloch@icn.siemens.com