This is the mail archive of the gdb@sourceware.org mailing list for the GDB 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]

PT_TEXT_ADDR on ARM


Hi,

I'm a bit unsure on how to proceed here: ARM has two different
definitions for PT_TEXT_ADDR, "49*4" in 2.4 uClinux and "0x10000" in
current Linux, which appears to be used on systems without a MMU as
well. The former definition "emulates" the behaviour of the Coldfire
port, and I've made a working gdbserver for such a system by simply
enabling the #ifdef'd code in linux-low.c, however that will most likely
fail on more recent kernels.

I'd like to prepare a patch that ideally fixes both 2.4 uClinux and 2.6
uClinux (normal Linux doesn't really need the offsets). Should I

 a) check the kernel version
 b) try 0x10000 first, if it returns zero, use the value from 0xc4
 c) use 0x10000 only?

   Simon


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