This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Prelinking on ARM with Debug Link


> Am 16.02.2016 um 11:08 schrieb Mark Wielaard <mjw@redhat.com>:
> 
> OK. Which other options are necessary?
> In particular in your cmd.sh you seem to be using -a arm -B
> CROSS_COMPILE=arm-none-linux-gnueabi- and -B CONFIG_DEBUG_INFO=y
> Is there a reason to use those options to reproduce the issue? I am
> particularly trying to figure out if you need or are using a cross build
> and if so between which architectures.
> 
> Thanks,
> 
> Mark

Hi Mark,

Iâve a cross compile environment.

-a arm is necessary to choose the right architecture.
-B CROSS_COMPILE=arm-none-linux-gnueabi- sets the compiler prefix for the Linux kernel compilation.

-B CONFIG_DEBUG_INFO=y is not necessary.

The target architecture is 32bit ARM. The host architecture is 64bit X86. Thatâs the reason why field .sec_load_offset is initialised with a 64bit wide hexadecimal number. But as the field .sec_load_offset is defined only as âunsigned longâ, the compiler complains. As a work around I tried to output decimal number instead for the initialisation of .sec_load_offset. I can compile alright. But the resulting backtrace calculations shown in my previous example produce strange results.

Kind Regards,
Torsten


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]