behavior of "strip -N"

Adam Megacz adam@megacz.com
Tue Jan 29 10:29:00 GMT 2002

Previous message (by thread): [PATCH] Unify messages in coff-arm.c and elf32-arm.h
Next message (by thread): behavior of "strip -N" [[ added an example ]]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,

I've noticed that when I strip a global symbol using strip -N and then
link with --noinhibit-exec, the locations where that symbol's address
would have been written get a 0x0 instead.

However, when I strip a file-local symbol, those locations seem to get
written with the address of the start of the section they fall in.

Is there any way to get the first behavior (0x0) when stripping
file-local symbols?

Context: I'm writing a post-compile, pre-link processor for
applications compiled with gcj (the GNU java-to-native-code static
compiler). The processor does high-level reachability analysis and
prunes unreachable methods and classes. There are some cases where I
need a 0x0 to be written into the code where the address of a deleted
method/class would have formerly lived. No, I can't integrate this
into the compiler.

  - a

Previous message (by thread): [PATCH] Unify messages in coff-arm.c and elf32-arm.h
Next message (by thread): behavior of "strip -N" [[ added an example ]]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Binutils mailing list