[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: firefox dumping core after NetBSD upgrade
On Fri, 11 Oct 2019 08:27:31 -0700 (PDT)
Paul Goyette <paul%whooppee.com@localhost> wrote:
> Core was generated by `firefox'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0x00007af20d009a7b in _atomic_cas_ptr (new=<optimized out>,
> at /build/netbsd-local/src_ro/lib/libpthread/arch/x86_64/pthread_md.h:77
> 77 __asm __volatile ("lock; cmpxchgq %2, %1"
> [Current thread is 1 (process 1)]
void *atomic_cas_ptr(volatile void *ptr, void *old, void *new);
So assuming setting old to NULL is allowed, then I guess either ptr or
new are pointing to invalid memory locations.
Can you step through the first 5 frames and see if you can narrow down
which pointer is corrupt? You have debug symbols for NetBSD libraries.
Main Index |
Thread Index |