On Sat, Mar 21, 2015 at 11:20:26AM +0200, Ivan A. Kosarev wrote:
> On 03/21/2015 03:02 AM, Konstantin Belousov wrote:
> > On Fri, Mar 20, 2015 at 03:59:52PM +0200, Ivan A. Kosarev wrote:
> >> #12 0x00000008011b428d in malloc_init_hard () at jemalloc_jemalloc.c:698
> >> #13 malloc_init () at jemalloc_jemalloc.c:296
> >> #14 0x0000000801243ea2 in ?? () from /lib/libc.so.7
> >> #15 0x00000008006a5400 in ?? ()
> >> #16 0x000000080089e5b0 in ?? () from /libexec/ld-elf.so.1
> >> #17 0x00007fffffffe0b0 in ?? ()
> >> #18 0x0000000801139d06 in _init () from /lib/libc.so.7
> >> #19 0x00007fffffffe0b0 in ?? ()
> > The backtrace is strange. Did you compiled malloc with the debugging
> > symbols, while keep rest of libc without -g ?
> I've just added the -g flag to CC_FLAGS in the Makefile and made sure to
> install an unstripped version of the .so . I could investigate more on
> why the early calls omit debug symbols, if it does any matter.
I want to understand at what stage of the initialization the access happens.
This is why I want to see the complete backtrace.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"