Re: systematic debugging of random freeze in debug mode

Tech-Archive recommends: Fix windows errors by optimizing your registry

<revyakin@xxxxxxxxx> wrote in message
news:1132624140.364337.219740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> even though I found what causes the trouble, Interestingly, I found
> that both the stack call and the break call don't always point to the
> actual process/dll causing the problem. I wonder what it means.

There are probably several threads. Your code is on one of them, some
unrelated system code runs on the others. Open Threads window, find your
primary thread, switch to it and you'll get correct call stack.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925


.

Relevant Pages

  • Re: Mysterious crash in LIBC06B4.DLL
    ... function without trouble, the function completes... ... the instant it tries to return to the calling procedure. ... As expected with stack memory overrun. ...
    (comp.os.os2.programmer.misc)
  • Re: Building my own freestanding start-up and library
    ... magically appears in front of Nate Eldredge: ... for taking the trouble to track down the problem for me, ... you push more values onto the stack, you need to add the number of ... the stack by the caller. ...
    (comp.unix.programmer)
  • Re: [OT] PostLisp, a language experiment
    ... > optional unless they must override precedence. ... > the correct number of arguments, so if there is mismatch, the user stack ... If you're having trouble with stack errors you're ...
    (comp.lang.lisp)
  • Re: Return values from functions
    ... goodTweetieBird wrote: ... that is on the stack. ... With sufficient thrust, pigs fly just fine. ... -- RFC 1925 ...
    (microsoft.public.vc.language)
  • Re: current function / sub name ?
    ... I think the trouble I was having ... Use Exceptions - you can get a full call stack... ...
    (microsoft.public.dotnet.languages.vb)