Re: weird Windows 2000/XP bug

From: surya (surya@nsecure.net)
Date: 11/01/01 

Message-ID: <00b401c16288$348525a0$5d00a8c0@nsecure>
From: "surya" <surya@nsecure.net>
To: <vuln-dev@securityfocus.com>, "ALoR" <Alor@iol.it>
Subject: Re: weird Windows 2000/XP bug
Date: Thu, 1 Nov 2001 09:18:29 +0530

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
|

Relevant Pages

  • Re: Nasty bug in the C# compiler, it truncates values on the stack
    ... Find great Windows Forms articles in Windows Forms Tips and Tricks ... >> If you change the function Bug() and make bool b = true it works fine. ... >> compiler will always truncate the struct on the stack to 1 byte. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: DDD and modules
    ... debugger rather than tons of 'write'. ... and gdb and ddd to debug, all on a windows box using cygwin. ... the compiler bundled appears to ...
    (comp.lang.fortran)
  • Re: Code Alignment Problem
    ... > is substantially different in debug and release modes. ... > you encountered a bug in the compiler or a timing problem. ... you need to understand the assembly code to track ...
    (microsoft.public.development.device.drivers)
  • Re: no debug info
    ... To ease debugging, the compiler does not optimize the code in a debug build. ... One is that your program has uncoverered a bug in the optimizer. ...
    (microsoft.public.vc.language)
  • Re: Lines of Codes - how many is enough?
    ... Apparently ADOM has over 185,000 lines of code. ... Windows has over 2 ... Maybe there's a bug in the compiler itself!" ...
    (rec.games.roguelike.development)