Hello,

when I debug my driver and something went wrong, I can't see (with
WinDBG) that the code inside finally{} is executed.

AFAIK the code inside finally is _always_ executed, so I assume that
WinDBG isn't following. Is this true?

Thank you for your efforts!
--

phren

Re: Does WinDBG follow into SEH finally{}? by Doron

Doron
Fri Apr 22 11:01:20 CDT 2005

did you compile your driver as optimized (ie a free build)?. if you so, the
source code does not match the execution 1:1 since the compiler has probably
rearranged the code. Yes, WinDBG follows in SEH properly.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"phren yohng" <no@spam.com> wrote in message
news:MPG.1cd1a8171d16b6ea9896bb@news.t-online.de...
> Hello,
>
> when I debug my driver and something went wrong, I can't see (with
> WinDBG) that the code inside finally{} is executed.
>
> AFAIK the code inside finally is _always_ executed, so I assume that
> WinDBG isn't following. Is this true?
>
> Thank you for your efforts!
> --
>
> phren



Re: Does WinDBG follow into SEH finally{}? by Maxim

Maxim
Fri Apr 22 11:34:17 CDT 2005

By default, even checked builds are optimized. Add this to the SOURCES file
to avoid it.

!IF !$(FREEBUILD)
MSC_OPTIMIZATION=/Od
!ENDIF

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"phren yohng" <no@spam.com> wrote in message
news:MPG.1cd1a8171d16b6ea9896bb@news.t-online.de...
> Hello,
>
> when I debug my driver and something went wrong, I can't see (with
> WinDBG) that the code inside finally{} is executed.
>
> AFAIK the code inside finally is _always_ executed, so I assume that
> WinDBG isn't following. Is this true?
>
> Thank you for your efforts!
> --
>
> phren