Re: Exception in my application

From: Oleg Starodumov (oleg_staro_at_hotmail.com)
Date: 08/23/04

  • Next message: Hendrik Schober: "Re: Symbol server woes" 
    Date: Mon, 23 Aug 2004 12:41:38 +0300

    It would be useful to see the call stack at the moment of the exception.
    Good debug symbols for system DLLs will be needed
    (now there are no symbols for system DLLs on your system,
    so the call stack will not be correct, probably).

    Since it is not too straightforward to configure VC6 debugger to use
    the latest system symbols, may be it is better to download
    WinDbg debugger and reproduce the problem with it:

    You can download it here (Debugging Tools for Windows package):
    http://www.microsoft.com/whdc/ddk/debugging/default.mspx

    Run the application under WinDbg, and when it stopped at the given
    breakpoint, run these commands:
    .symfix
    .reload /f
    kv

    and post here the output of kv command. (Note that .reload will cause
    symbols to be downloaded from Microsoft's symbol server)

    (Btw, here is an example of using WinDbg to download symbols
    for VC6 debugger:
    http://users.rcn.com/jenjordi/jordi/symbols.html
    (with one addition: if you work on Windows 2000, you should also copy
    downloaded .DBG files, in addition to .PDB files;
    and AFAIK it is also unnecessary to modify any Registry settings on Windows 2000)

    Also try to run the application under Full PageHeap (since heap corruption
    is a possible reason):

    1) In the installation directory of Debugging Tools, find GFlags utility
    and run it as the following:
    gflags -p /enable YourApp.exe /full
    (replace YourApp.exe with the real name of your executable)
    2) Run the application under debugger (e.g. Visual Studio debugger).
    If PageHeap detects a problem, it will raise an access violation or a hard-coded
    breakpoint. See also Debug Output window for additional messages
    from PageHeap.

    More information about PageHeap:
    http://support.microsoft.com/default.aspx?scid=kb;en-us;286470

    Regards,
    Oleg

  • Next message: Hendrik Schober: "Re: Symbol server woes"

    Relevant Pages

    • Re: Breakpoint instantiation
      ... don't have any debugger configured in the Target Device Connctivity ... so I can download the image. ... Also I cannot connect to the device with the remote tools. ... Could the breakpoint problem be related with this? ...
      (microsoft.public.windowsce.platbuilder)
    • Re: Breakpoint on Operative system
      ... All the info you need to configure the device and download the ... Luca Calligaris ... Build Options -> Enable kernel debugger. ... I have enabled KITL and connect my board through ethernet, ...
      (microsoft.public.windowsce.platbuilder)
    • Re: Breakpoint on Operative system
      ... All the info you need to configure the device and download the ... Luca Calligaris ... Image is too large for current RAM and RAMIMAGE settings ... Build Options -> Enable kernel debugger. ...
      (microsoft.public.windowsce.platbuilder)
    • Re: Cant attach to process on CE device
      ... Debugger" option is checked or not. ... and then download the image from Platform Builder. ... Error Messages: ...
      (microsoft.public.windowsce.embedded.vc)
    • Re: debugger exception
      ... VS6 cannot use symbol server automatically, ... run SymChk like this: ... so that VC6 debugger will be able to find them; ... You can get a couple of FAILED messages, because not all system DLLs ...
      (microsoft.public.vc.mfc)