Not setting a vendor code before use would be invalid which we tried to
catch. But to detect that we do need to initialize the vendor array to
zero first.
Signed-off-by: Mark Wielaard
---
src/ChangeLog | 5 +
src/readelf.c | 1 +
2 files changed, 6 insertions(+)
diff --git a/src/ChangeLog b
Signed-off-by: Mark Wielaard
---
backends/ChangeLog| 5 +
backends/aarch64_symbol.c | 9 ++---
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/backends/ChangeLog b/backends/ChangeLog
index 4ea1acd..a742eb2 100644
--- a/backends/ChangeLog
+++ b/backends/ChangeLog
@@
On Tue, 2014-01-14 at 10:07 +0100, Jan Kratochvil wrote:
> On Tue, 14 Jan 2014 10:00:59 +0100, Mark Wielaard wrote:
> > The __GLOBAL__.[ID]_xxx functions are wrappers generated when a module
> > xxx contains constructors and destructors of static objects, which will
> > call the actual static initi
On Tue, 14 Jan 2014 10:00:59 +0100, Mark Wielaard wrote:
> The __GLOBAL__.[ID]_xxx functions are wrappers generated when a module
> xxx contains constructors and destructors of static objects, which will
> call the actual static initialization and destruction functions for all
> globals in the modu
On Mon, 2014-01-13 at 23:17 +0100, Jan Kratochvil wrote:
> for example currently plain symbol "f" (for function f()) gets printed in the
> backtrace as "float" (as for a function float()).
Nice catch.
> I am not completely sure about DCT_GLOBAL_CTORS and DCT_GLOBAL_DTORS but I
> could not find a