I'm thinking that we had a problem similar to this when we installed something after putting in copyover. Let me research it for you and see what I come up with.
Vertigo > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Dale Kingston > Sent: Saturday, May 10, 2003 12:36 AM > To: [email protected] > Subject: Odd startup problem > > > Ok I'm having an odd problem with starting up my mud. And I > don't know where to begin looking on how to fix this. Here is > what GDB is telling me what > happened: > > (gdb) bt > #0 0x0832fdd5 in ?? () > #1 0x080a2a8c in main (argc=2, argv=0xbfffe324) at > comm.cc:777 #2 0x40078336 in __libc_start_main > (main=0x80a27a0 <main>, argc=2, > ubp_av=0xbfffe324, init=0x80493ec <_init>, fini=0x81d0824 <_fini>, > rtld_fini=0x4000d2fc <_dl_fini>, stack_end=0xbfffe31c) > at ../sysdeps/generic/libc-start.c:129 > (gdb) fram 1 > #1 0x080a2a8c in main (argc=2, argv=0xbfffe324) at comm.cc:777 > 777 control = init_socket(port); > (gdb) list > 772 game_loop_mac_msdos( ); > 773 #endif > 774 > 775 #if defined(unix) > 776 if (!fCopyOver) /* We have already the port > if copyover'ed > */ > 777 control = init_socket(port); > 778 > 779 boot_db( ); > 780 > 781 #ifdef IMC3 > > I just recently wrote some bind code, for like bind points > and an editor so we can edit them online. But I can't see how > that could be affecting the mud before main has even left. > It's barly initializing the port when it kills off. > > Any help on this would be much appericiated. > > > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom >
