RE: zmailer 2.99.49 router bus errors on FreeBSD 2.1.7

[Gennadi Makhmetov <gena@ph-elec.phys.msu.su>]

On 17-Jun-97 Matthew C. Mead wrote:
>    I'm not sure if this is what's going on in router when a piece of
>mail gets shoved to it, but this should at least be a start.  This is
>the result of running router -i under gdb and doing a "router you"
>
>    Any help would be appreciated.  Thanks.
>
>
>
>-matt
>
>
>(gdb) run -i
>Starting program: /usr/local/zmailer/bin/router -i
>ZMailer router (2.99.49 #1: Tue Jun 17 13:50:42 EDT 1997)
>  mmead@goof.com:/goof/goof/home/mmead/zmailer-2.99.49/router
>Copyright 1992 Rayan S. Zachariassen
>Copyright 1992-1997 Matti Aarnio
>
>z# router you
><mmead.interactive@goof.com>: address: you
>
>Program received signal SIGBUS, Bus error.
>0x3d4c7 in free (cp=0x81dd4) at malloc.c:387
>387                     UNLINK(p1, bin);
>(gdb) where
>#0  0x3d4c7 in free (cp=0x81dd4) at malloc.c:387
>#1  0x28c60 in sb_free (n=0) at execute.c:785
>#2  0x2944e in runio (ioopp=0xefbf9d30) at execute.c:1016
>#3  0x28605 in execute (c=0xefbf9d08, caller=0xefbfadb0, oretcode=0, 
>    name=0x1bb1e "<builtin cmd>") at execute.c:520
>#4  0x1bd1b in runcommand (c=0xefbf9d08, pc=0xefbfadb0, retcodep=0xefbfa6c0, 
>    cmdname=0x0) at interpret.c:682
>#5  0x1ddae in interpret (Vcode=0x78044, Veocode=0x7a228, Ventry=0x7834a, 
>    caller=0xefbfadb0, retcodep=0xefbfa6c0, cdp=0x72dd0) at interpret.c:1679
>#6  0x28011 in execute (c=0xefbfadb0, caller=0xefbfbd38, oretcode=0, 
>    name=0x1bb1e "<builtin cmd>") at execute.c:412
>#7  0x1bd1b in runcommand (c=0xefbfadb0, pc=0xefbfbd38, retcodep=0xefbfb6d8, 
>    cmdname=0x7833b "routeuser") at interpret.c:682
>#8  0x1ddae in interpret (Vcode=0x7c7f8, Veocode=0x7d8db, Ventry=0x7c900, 
>    caller=0xefbfbd38, retcodep=0xefbfb6d8, cdp=0x76f28) at interpret.c:1679
>#9  0x28011 in execute (c=0xefbfbd38, caller=0xefbfccc0, oretcode=0, 
>    name=0x1bb1e "<builtin cmd>") at execute.c:412
>#10 0x1bd1b in runcommand (c=0xefbfbd38, pc=0xefbfccc0, retcodep=0xefbfc6f0, 
>    cmdname=0x7c8f3 "rrouter") at interpret.c:682
>#11 0x1ddae in interpret (Vcode=0x732f4, Veocode=0x73ce5, Ventry=0x73b58, 
>    caller=0xefbfccc0, retcodep=0xefbfc6f0, cdp=0x67634) at interpret.c:1679
>#12 0x28011 in execute (c=0xefbfccc0, caller=0x4fe7c, oretcode=0, 
>    name=0x1bb1e "<builtin cmd>") at execute.c:412
>#13 0x1bd1b in runcommand (c=0xefbfccc0, pc=0x4fe7c, retcodep=0xefbfd67c, 
>    cmdname=0x73b4c "router") at interpret.c:682
>#14 0x1ddae in interpret (Vcode=0x7baf0, Veocode=0x7bb01, Ventry=0x0, 
>    caller=0x4fe7c, retcodep=0xefbfd67c, cdp=0x7b4b4) at interpret.c:1679
>#15 0x30f2b in zshtoplevel (errname=0x0) at zmsh.c:79
>#16 0x1f95 in main (argc=2, argv=0xefbfd748) at router.c:308
>
>
>-- 
>Matthew C. Mead                                        Technology Support Staff,
>                                               Mathematics Department,
>mmead@math.vt.edu                              Virginia Tech
>(540)231-2643

I had the same problem. It was solved by doing configure with option 
--with-system-malloc

---------------------------------
E-Mail: "Gennadi Makhmetov" <gena@ph-elec.phys.msu.su>
Date: 18-Jun-97
Time: 20:39:22