reactos-kernel

[ros-kernel] wcstomb(s).c warnings

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

wcstombs.c(91):

   if (wc < 0 || wc > 0x7fffffff)

shouldn't this be:

   if ( wc & 0x80000000 )


same thing in wcstomb.c(87)

   if (wc < 0 || wc > 0x7fffffff)


Now that I think about it, I think this won't
fix the warning, because the warning is
that expression is always false because of
limited range of type.

Perhaps the check should really bw:

   if ( wc & 0x8000 )

since wchar_t is supposed to be 16-bit?

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

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

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...

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
>

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

[Eric K. <ek...@rz...>]

"Royce Mitchell III" <ro...@ev...> wrote:

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

Please try a clean rebuild of the current CVS tree. David fixed some severe
bugs and I got my 9 year old Seagate ST3144A (130 MB) running which reported
576 byte sectors. ;-)

Eric

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

[David W. <we...@cw...>]

On Tue, Jul 16, 2002 at 10:26:26PM -0500, Royce Mitchell III wrote:
> Any ideas? 
>
Yes, ntoskrnl is an exception, just add 0xc0000000 to the printed 
address when using addr2line. I'm sorry figuring out where the kernel crashed
can be such a bear.

> It is still reporting div/0 by the way, and I have latest CVS...
> 
Seems to be working here.