Re: Code Alignment Problem
From: Ken Allen (kendrhyd_at_sympatico.ca)
Date: 02/04/05
- Next message: Ken Allen: "Re: Code Alignment Problem"
- Previous message: Gregg: "Windbg shows only ntoskrnl.exe"
- In reply to: cristalink: "Re: Code Alignment Problem"
- Next in thread: cristalink: "Re: Code Alignment Problem"
- Reply: cristalink: "Re: Code Alignment Problem"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 04 Feb 2005 16:12:52 -0500
cristalink wrote:
> The environment does not really matter. The code generated by the compiler
> is substantially different in debug and release modes. Most likely you have
> a bug in your code, such as an uninitialized variable etc. There's a chance
> you encountered a bug in the compiler or a timing problem.
>
> Review your code. Run Prefast from the latest DDK on your sources. Try
> Driver Verifier. Usually, you need to understand the assembly code to track
> down such a bug. If you cannot read assembly code, you better hire an
> expert.
>
Perhaps I was not clear -- the ability to make the problem disappear and
reappear by the addition and removal of debug code exists in the debug
build only. IN one debug build the problem will exist; if I add some
additional statements, the problem does not manifest itself!
-Ken
- Next message: Ken Allen: "Re: Code Alignment Problem"
- Previous message: Gregg: "Windbg shows only ntoskrnl.exe"
- In reply to: cristalink: "Re: Code Alignment Problem"
- Next in thread: cristalink: "Re: Code Alignment Problem"
- Reply: cristalink: "Re: Code Alignment Problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|