On Mon, Jul 06, 2015 at 06:02:11PM -0500, Larry Rosenman wrote:
I've enabled DEBUG_REDZONE, and have DEBUG_MEMGUARD in the system, but
have zero clue as to what to set for memguard :(
Could I get some guidance?
On 2015-07-06 17:43, K. Macy wrote:
That's really disturbing, but
On Tue, Jul 07, 2015 at 08:50:15AM -0500, Larry Rosenman wrote:
On 2015-07-07 08:36, Konstantin Belousov wrote:
On Tue, Jul 07, 2015 at 08:02:39AM -0500, Larry Rosenman wrote:
(kgdb) #0 doadump (textdump=1) at pcpu.h:221
#1 0x80a95445 in kern_reboot (howto=260)
at
On 2015-07-07 09:18, Konstantin Belousov wrote:
On Tue, Jul 07, 2015 at 08:50:15AM -0500, Larry Rosenman wrote:
On 2015-07-07 08:36, Konstantin Belousov wrote:
On Tue, Jul 07, 2015 at 08:02:39AM -0500, Larry Rosenman wrote:
(kgdb) #0 doadump (textdump=1) at pcpu.h:221
#1 0x80a95445
On Tue, Jul 07, 2015 at 11:08:02AM +0300, Konstantin Belousov wrote:
First reproduce the issue without the vbox modules loaded.
Done:
borg.lerctr.org dumped core - see /var/crash/vmcore.7
Tue Jul 7 07:52:39 CDT 2015
FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r285159M: Mon
On Tue, Jul 07, 2015 at 08:02:39AM -0500, Larry Rosenman wrote:
(kgdb) #0 doadump (textdump=1) at pcpu.h:221
#1 0x80a95445 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:447
#2 0x80a95a38 in vpanic (fmt=value optimized out,
ap=value optimized out)
On 2015-07-07 08:36, Konstantin Belousov wrote:
On Tue, Jul 07, 2015 at 08:02:39AM -0500, Larry Rosenman wrote:
(kgdb) #0 doadump (textdump=1) at pcpu.h:221
#1 0x80a95445 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:447
#2 0x80a95a38 in vpanic
actually, the following are interesting further down:
#13 0x808af473 in sys_write (td=0xdeadc0dedeadc116,
uap=value optimized out) at /usr/src/sys/kern/sys_generic.c:398
#14 0x80b57a6d in amd64_syscall (td=0xf80736fda4c0,
traced=0)
at subr_syscall.c:133
the td
I've enabled DEBUG_REDZONE, and have DEBUG_MEMGUARD in the system, but
have zero clue as to what to set for memguard :(
Could I get some guidance?
On 2015-07-06 17:43, K. Macy wrote:
That's really disturbing, but could be an artifact of limitations in debug
info fidelity. If curthread
That's really disturbing, but could be an artifact of limitations in debug
info fidelity. If curthread is corrupt I would expect things to blow up
almost instantly.
Try enabling memguard for the zone or mtype for the object that has the
corrupt mutex field.
-K
On Jul 6, 2015 5:48 AM, Larry
I've gotten a couple of these:
borg.lerctr.org dumped core - see /var/crash/vmcore.3
Sun Jul 5 16:32:12 CDT 2015
FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r285159: Sun Jul
5 09:35:33 CDT 2015 r...@borg.lerctr.org:/usr/obj/usr/src/sys/LER amd64
panic: general
The value of the mutex in the stack trace indicates that it's a use after
free. There are various memory debugging options (memguard, redzone) that
may help track it down.
-K
On Jul 5, 2015 2:37 PM, Larry Rosenman l...@lerctr.org wrote:
I've gotten a couple of these:
borg.lerctr.org dumped
11 matches
Mail list logo