Re: weird Windows 2000/XP bug

["surya" <surya () nsecure net>]

HI,
    The problem is in the cmd.exe, it has the debug symbols
in it and it causes the reboot. remember, for
    dir
    dir
    dir
    f9
    f9
    f9
    f9 .....

it gives the blue screen with the debug messages.

Anyway, i have compiled the program in LCC and  gives
the same result. I think compiler doesnot make much difference.
Anything that support windows would be producing the same
results. Old MS-DOS compiler create the executables in the
DOS Format, but i guess it runs on a separate VM Processor
under the command prompt of NT. I haven't checked with compiling
the same program under Turbo C Version 2.0 or 3.X. Can anybody
please?

regards,
surya
nSecure Software (p) Ltd
IN

----- Original Message -----
From: "ALoR" <Alor () iol it>
To: <vuln-dev () securityfocus com>
Sent: Wednesday, October 31, 2001 04:44 am
Subject: re: weird Windows 2000/XP bug


| At 19.47 30-10-2001, awe () centrum cz wrote:
| >Hi,
| >I've traced this and problem is in API function WriteFile, further
| >in some NT internal call (int 2E), it only occurs when console is
|
| I've traced it with the VC++ debugger and it crasched on ExitProcess()
| after the printf.
| but the really amazing thing is that debugging it another time let me no
crash.
| again and it crashed in the CRT I/O routines.
|
| I can't find the exact point of failure.
| it seems to me that the effect is in some way random...  Infact not always
| the machine restart or crash, sometime it closes the application
succesfully.
|
| I'll debug it better tomorrow.
|
| bye
|
|     --==> ALoR <==---------------------- -  -   -
|
|   ettercap project : http://ettercap.sourceforge.net
|   e-mail: alor (at) users (dot) sourceforge (dot) net
|