NewLC - strange problem while debuggging - Comments

Re: strange problem while debuggging

alh — Thu, 30 Nov 2006 08:51:30 +0100

I strongly suspect your threads then...
Or the method you use to make sure they are killed.

Do they share any memory?

what functions do you see in the callstack?

Re: strange problem while debuggging

saurabh_gyl — Thu, 30 Nov 2006 06:55:06 +0100

i am not using any asynchronous call at the moment...though i have a few thread in my application. but before exit i have made sure that those threads are killed. moreover my UI is minimal just a simple hello world

Re: strange problem while debuggging

alh — Wed, 29 Nov 2006 11:05:56 +0100

If you application uses asyncronous calls, how deep you debug can change the timeing of things.

Requests not finising in time or finishing earlier..

Not seeing your code in the call stack suggests it is something in the framework you mess up. Can be all kinds of reasons.

Re: strange problem while debuggging

saurabh_gyl — Wed, 29 Nov 2006 09:42:34 +0100

still my question reamins there tht am i getting different outcomes depnding on how deep i debug...

Re: strange problem while debuggging

sirisha — Wed, 29 Nov 2006 06:38:56 +0100

why dont u try using hooklogger.
May be u have deleted a variable teice which leads to memory leak.
Check out ur code.
Cheers
Sirisha

Re: strange problem while debuggging

saurabh_gyl — Tue, 28 Nov 2006 09:16:16 +0100

i understand your point but am using debugger in both the cases...in one caswe am only debugging exe and dll while in other am debugging only exe.

and in first case before getting kern-exec -3 panic i was getting alloc(mem leaks) which all i have removed.

so it is still not clear that why is there a mem leak if i am only debugging exe and not both. and from where the hell is this kern-exec 3 panic coming(i cannot see any of my code in callstack).

all comments are welcome

Re: strange problem while debuggging

rbrunner — Tue, 28 Nov 2006 08:31:01 +0100

There are rare cases where the mere presence of a debugger can alter the behaviour of a program.

According to my experience this mostly happens in connection to uninitialized variables that have an upredictable value, but e.g. always the same when the program is running alone, and another one when the program and the debugger are running together (e.g. because the program is loaded at another location in memory when loaded under the control of the debugger.)

E.g. you have a boolean that you not properly initialize in your program; if your program runs alone it happens to have a value of True, if your program shares the memory with the debugger it happens to have a value of False.

strange problem while debuggging

saurabh_gyl — Tue, 28 Nov 2006 06:57:49 +0100