https://sourceware.org/bugzilla/show_bug.cgi?id=31460
--- Comment #5 from Vladimir Mezentsev
---
The problem is:
We use pthread_getspecific() and pthread_setspecific() to access thread local
memory.
We use this memory to check that our interposed functions (like malloc, calloc
or free) don't hav
https://sourceware.org/bugzilla/show_bug.cgi?id=31527
Bug ID: 31527
Summary: gdb is not working for UNC path
Product: binutils
Version: 2.43 (HEAD)
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bin
https://sourceware.org/bugzilla/show_bug.cgi?id=31460
--- Comment #4 from Vladimir Mezentsev
---
It looks like the bug is in gprofng/libcollector/heaptrace.c.
I see that init_heap_intf() is not thread safe.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=31115
--- Comment #8 from Jan Beulich ---
(In reply to Nick Clifton from comment #5)
> > There's another thing I just discovered : I can reproduce GDB's bad
> > behavior on an ELF executable (produced by GCC from the .S file), but
> > not on a .o fi
https://sourceware.org/bugzilla/show_bug.cgi?id=31460
--- Comment #3 from James Carlson ---
I found a clue: the application uses libtcmalloc. It seems like this recursion
problem happens when that library is either ldopen'd into the address space or
LD_PRELOADed in.
--
You are receiving this ma
https://sourceware.org/bugzilla/show_bug.cgi?id=31460
--- Comment #2 from James Carlson ---
First of all, your test case:
% gcc -pthread t.c
t.c:3:11: warning: built-in function 'calloc' declared as non-function
[-Wbuiltin-declaration-mismatch]
3 | long long calloc = 0;
| ^~~
Hi Vijay,
but Im unsure about PT_TLS segment consisting only of .tbss section like in
above case.
Why ? It seems reasonable to me.
when objcopy does consider such a segment to be part of LOAD, when assigning
offsets things seem to be going wrong
First issue we encounter.
objcopy: stq0GB
