On 9/21/05, Valnir <[EMAIL PROTECTED]> wrote:
> I ran the following command from my area directory (where the CORE was
> created).
>
> Gdb -c core ../src/v5

Then that's obviously not working.

> And NO, it's not always in the same place. I've seen it in a couple of
> files, including bit.c and some others.

You've a Heisenbug. Probably unallocated or freed memory is being
written somewhere. Look over recently changed code, since it might not
be the kernel upgrade. Good luck :)

-David

> - Valnir
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Wilson
> Sent: Wednesday, September 21, 2005 1:34 AM
> To: [email protected]
> Subject: Re: Crash issues.
>
> You should run gdb from inside your source directory (I think) so that it
> can pull out the contents of the source files.
>
> Does it always crash in the same place?
>
> -David
>
> On 9/20/05, Valnir <[EMAIL PROTECTED]> wrote:
> > Ever since WolfPaw upgraded they kernals and enabled the CPU and
> > memory pooling we have been getting weird crashes. I've posted the
> > contents of the latest core below to show what I mean. Any help would
> > be appreciated. And YES, I have done a clean make since then, several.
> >
> > #0  0x080df254 in spell_chain_lightning (sn=36, level=73,
> > ch=0x41d8a754, vo=0x41bb7e60, target=0) at magic.c:1270
> > 1270    magic.c: No such file or directory.
> >         in magic.c
> > (gdb) where
> > #0  0x080df254 in spell_chain_lightning (sn=36, level=73,
> > ch=0x41d8a754, vo=0x41bb7e60, target=0) at magic.c:1270
> > #1  0x08109092 in spec_cast_adept (ch=0x41d8a754) at special.c:623
> > #2  0x0810ca78 in mobile_update () at update.c:600
> > #3  0x081102cd in update_handler (forced=0 '\0') at update.c:2036
> > #4  0x0809c405 in game_loop_unix (control=4) at comm.c:892
> > #5  0x0809bcf8 in main (argc=4, argv=0xb6fbd734) at comm.c:485
> > #6  0x40fe3d06 in __libc_start_main () from /lib/libc.so.6
> >
> > Thanks in advance to everyone!
> >
> > - Valnir
> >
> >
> > --
> > ROM mailing list
> > [email protected]
> > Unsubscribe here ->>> http://www.rom.org/cgi-bin/mailman/listinfo/rom
> >
> --
> ROM mailing list
> [email protected]
> Unsubscribe here ->>> http://www.rom.org/cgi-bin/mailman/listinfo/rom
>
>
> --
> ROM mailing list
> [email protected]
> Unsubscribe here ->>> http://www.rom.org/cgi-bin/mailman/listinfo/rom
>

Reply via email to