Re: Netgraph malloc(9) trouble...

Ok, found it, looks like ancient damage.

Poul-Henning

In message <87190.1087144785_at_critter.freebsd.dk>, Poul-Henning Kamp writes:
>
>panic: malloc(9)/free(9) confusion.
>Probably freeing with wrong type, but maybe not here.
>Debugger("panic")
>Stopped at      Debugger+0x45:  xchgl   %ebx,in_Debugger.0
>db> trace
>Debugger(c061e146) at Debugger+0x45
>panic(c061c849,c061c813,c0530c81,0,1) at panic+0xbb
>free(c0bc9cc0,c06520c0,0,c0bc9cc0,0) at free+0x116
>ngmn_rcvmsg(c0aeea00,c0bc9d00,0,0,0) at ngmn_rcvmsg+0x2d1
>ng_generic_msg(c0aeea00,c0bc9d00,0,7d1,c0aeea58) at ng_generic_msg+0x11d8
>ng_apply_item(c0aeea00,c0bc9d00) at ng_apply_item+0x312
>ng_snd_item(c0bc9d00,0,0,c0b502e0,3d) at ng_snd_item+0x703
>ngc_send(c0e364f0,0,c0bab400,c0b6f120,0) at ngc_send+0x110
>sosend(c0e364f0,c0b6f120,c7fedc54,c0bab400,0) at sosend+0x4a1
>kern_sendit(c0be4000,3,c7fedccc,0,0) at kern_sendit+0x128
>sendit(c0be4000,3,c7fedccc,0,804f03d) at sendit+0x141
>sendto(c0be4000,c7fedd14,6,c,202) at sendto+0x4d
>syscall(2f,2f,2f,bfbfe297,bfbfe292) at syscall+0x217
>
>-- 
>Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
>phk_at_FreeBSD.ORG         | TCP/IP since RFC 956
>FreeBSD committer       | BSD since 4.3-tahoe
>Never attribute to malice what can adequately be explained by incompetence.
>_______________________________________________
>freebsd-current_at_freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk_at_FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.