Re: [ros-kernel] finally got good stack trace...

[Royce M. I. <ro...@ev...>]

I put a bunch of DbgPrint's all over that function last night, and didn't
see any of them on-screen...

----- Original Message -----
From: "Royce Mitchell III" <ro...@ev...>
To: <rea...@li...>
Sent: Tuesday, July 16, 2002 10:26 PM
Subject: [ros-kernel] finally got good stack trace...


> Here are the results. Kinda odd how four traces turn up the same line in
> irql.c...
>
> crashed on hal.dll 4228 ( udelay.c 94 )
>  WRITE_PORT_UCHAR((PUCHAR)(0x40+channel),
>     (unsigned char) temp);
>
> stack trace:
>
> ntoskrnl.exe 23e8 ( usercall.c 99 )
> ( closing } of KeAddSystemServiceTable )
>
> hal.dll 5694 ( irql.c 385 )
> hal.dll 56e8 ( irql.c 385 )
> hal.dll 57f3 ( irql.c 385 )
> hal.dll 580f ( irql.c 385 )
> ( closing } of HalEnableSystemInterrupt )
>
>
> Any ideas? It is still reporting div/0 by the way, and I have latest
CVS...
>
> I'm gonna add DbgPrint to find out what channel and temp it's crashing
on...
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Jabber - The world's fastest growing
> real-time communications platform! Don't just IM. Build it in!
> http://www.jabber.com/osdn/xim
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel
>