[Bug 204426] Processes terminating cannot access memory
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Jan 28 23:31:55 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204426
--- Comment #15 from rblayzor at inoc.net ---
After installing a new world and booting to new root NFS. I've seen one crash
(usually takes time). However this one is a bit odd. Kernel message:
Failed to write core file for process exim (error 14)
pid 58267 (exim), uid 26: exited on signal 11
But I do get a core file, but this is all:
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...
Core was generated by `exim'.
Program terminated with signal 11, Segmentation fault.
Cannot access memory at address 0x800978ac0
#0 0x00000008023a2990 in ?? ()
(gdb) bt full
#0 0x00000008023a2990 in ?? ()
No symbol table info available.
Cannot access memory at address 0x7fffffff4f70
(gdb) bt info
No symbol "info" in current context.
(gdb) x/i $rip
0x8023a2990: Cannot access memory at address 0x8023a2990
(gdb) info registers
rax 0xffffffffffffffd0 -48
rbx 0x2010 8208
rcx 0x800788330 34367636272
rdx 0x0 0
rsi 0x3ff3 16371
rdi 0x8030033c1 34410083265
rbp 0x7fffffff5420 0x7fffffff5420
rsp 0x7fffffff4f70 0x7fffffff4f70
r8 0x7fffffff4670 140737488307824
r9 0x80269f6e0 34400237280
r10 0xfffffffffffff000 -4096
r11 0x8030033c0 34410083264
r12 0x7fffffffed40 140737488350528
r13 0x803229000 34412335104
r14 0x2010 8208
r15 0x3000 12288
rip 0x8023a2990 0x8023a2990
eflags 0x10206 66054
cs 0x43 67
ss 0x3b 59
ds 0x0 0
es 0x0 0
fs 0x0 0
gs 0x0 0
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-threads
mailing list