Re: Application crash

On 17 Ott, 17:00, Joseph M. Newcomer <newco...@xxxxxxxxxxxx> wrote:
See below...



On Fri, 17 Oct 2008 04:08:05 -0700 (PDT), john wayne <attack...@xxxxxxxxx> wrote:
On 17 Ott, 05:12, Joseph M. Newcomer <newco...@xxxxxxxxxxxx> wrote:
First, you have used one of those common nonsense words, "crash".  Applications don't
"crash".  They exhibit very specific behavior, which may include reporting unhandled
exceptions, assertion failures, the simple disappearance of the application, runtime error
notifications, etc.  Until you explain what you saw, we cannot even BEGIN to suggest how
to look for it.

What do you mean "with the debugger it isn't possible to find it"?  If you enable
just-in-time debugging, when your app terminates for some error reason you are usually
given the option to enter the debugger.  Did this happen?  Did you enter the debugger?  If
so, what did you discover?

By the way, I currently have a program that doesn't work.  Can you tell me how to fix it?
[That's all you've said...]
                                        joe

Hi Joe and thanks for your answer. You seems my teacher when he
reproach me :D

By the way, I currently have a program that doesn't work.  Can you tell me how to fix it?
[That's all you've said...]

I disagree, sorry.

***
No, that's all you've said.  In the paragraph below, you say a tiny bit more, but not
nearly enough to be useful in diagnosing the problem.  
***

In anyway using VC debugger when the application has the error and
stop itself (it's ok so?) the debugger show me the only assembly code
"int 3". I can't retrieve the error in any line of the code. I think
there is a problem of array addressing but I don't know how to fix it.
The error not happen so often that permit me to see it easly

****
This is a debug break.  It is most commonly caused by a serious runtime error.  So what
came out before this happened?  If this is all that happened, are you running a debug or a
release version of the code?  What version of VS?  Did you load the C runtime sources on
your machine?  What is the call stack (it doesn't matter if you see an int3 in assembly
code; what is the symbolic location where it is found, what is the call stack to your
program, what were you doing in the program that created the path that lead here, etc.)?

If a debug version, this could also be a simple ASSERT breakpoint.  You still haven't said
what actually happens!

Without knowing the calls stack, very little is possible.

If this happens in a release version, see my essay "Surviving the Release Version" on my
MVP Tips site.  You need to create a symbol table for debugging (it is a fundamental
design flaw of earlier versions of VS that they fail to do this)

First guess is memory damage, that being one of the more frequent causes of what appear to
be spurious int3 stops, but did any message come out OTHER than just having the program
stop?  

Without real information, we can't help you debug it.
                        joe

Hi joe
the problem was in a variable initialization that is the index value
of an array. Now is all ok. I use VC++ 6 and in debug version

Thanks
.

Relevant Pages

  • Error: recommending debug
    ... new windows page, with out instructions for the next ... with "Runtime Error has occured. ... Do you wish to Debug?" ... >Do you want to debug using the selected debugger? ...
    (microsoft.public.windowsxp.general)
  • Re: Application crash
    ... exceptions, assertion failures, the simple disappearance of the application, runtime error ... What do you mean "with the debugger it isn't possible to find it"? ... This is a debug break. ... It is most commonly caused by a serious runtime error. ...
    (microsoft.public.win32.programmer.gdi)
  • Re: Application crash
    ... First, you have used one of those common nonsense words, "crash". ... exceptions, assertion failures, the simple disappearance of the application, runtime error ... What do you mean "with the debugger it isn't possible to find it"? ...
    (microsoft.public.win32.programmer.gdi)
  • Re: The application has requested the Runtime to terminate it in an unusual way, please contact the
    ... I have a MFC application programmed/complied/linked with VS2005, ... Runtime Error: ... Have you tried running a debug build in the debugger? ...
    (microsoft.public.vc.mfc)
  • Re: How to connect to children process
    ... Main problem is amount of manual operations required per debug cycle. ... connection to DLL with debugger takes sensible amount of time and manual ... Is the main problem that the debugger keeps symbols file loaded ... AFAIK that's how VS2003 debugger works, but WinDbg should usually ...
    (microsoft.public.vsnet.debugging)
Loading