This is the mail archive of the gdb-patches@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]

Re: [patch] validate binary before use


On 12-12-27 03:59 PM, Jan Kratochvil wrote:
On Thu, 27 Dec 2012 21:06:52 +0100, Aleksandar Ristovski wrote:
build-id would be great if it was required by the standard

GDB can check if it exists and do something as a fallback if it does not exist. Such as printing a warning and possibly also verifying the program headers, if compatibility with binaries from old toolchain and/or toolchain without configured ld --build-id is required in some situations (which I doubt).


and mapped into loadable segments.

It is mapped, because one of its purposes is to get dumped into a core file. In fact there is a special care to make it always present in the first page.

Ok I didn't know that (we are not using it). In any case, what I am trying to do does not disqualify build-id (I'll use it in fact, if present).


Note also that I really want a solution that does *not* rely on section headers but rather only on load-time required stuff.

Thanks,

Aleksandar


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