Re: [GD-General] problems while debugger is attached

[Andras B. <and...@gm...>]

Running with the debugger attached does not mean that I'm running a debug  
build. I can attach the debugger to any process, it does not matter how it  
was built. And this bug happens in both debug and release builds, so my  
guess is that it's not an uninitialized variable problem.

Thanks,

Andras

On Sun, 23 Jul 2006 15:29:34 -0600, Megan Fox <sha...@gm...> wrote:

> It may or may not be your problem, but I've had many cases where, due
> to the debugger assigning consistent values to uninitialized
> variables, the application fails - but if I allow those to remain
> uninitialized in release mode, it simply functions (on certain
> machines).  In general, that's the first thing I go looking for when I
> have a problem that shows in debug mode but not in release.  Usually,
> it ends up being me having somehow handed a function a bad pointer to
> nothing, rather than the structure I intended to send.
>
> On 7/23/06, Andras Balogh <and...@gm...> wrote:
>> I have a strange bug, where if I'm running the program without the
>> debugger attached (CTRL-F5 in VS), the program would run correctly both  
>> in
>> debug and release builds. But when I run the program with F5, so the
>> debugger is attached, then it blocks on a function call and never  
>> returns.
>> If I put a breakpoint before this call, and step through it, then
>> everything seems to work fine, and the function returns as expected..
>>
>> Could this be a deadlocking problem? Any ideas why attaching a debugger
>> makes any difference? And hints on how to debug this?
>>
>> Thanks,
>>
>>
>>
>> Andras