Re: Help tracking error

From: Mike Larson (MikeTheRed_at_Hotmail.com)
Date: 10/14/04 

Date: Thu, 14 Oct 2004 10:33:53 -0500

Thank you for the responce.

I will try to copy the files to the target system and see how that works.

I also have the offending addresses. How do you convert the addresses into
lines in the source code?

Thanks

Mike

"Oleg Starodumov" <oleg_staro@hotmail.com> wrote in message
news:eg4$HUcsEHA.2804@TK2MSFTNGP14.phx.gbl...
>
> > I have developed a VC++ app that I compile into a DLL for use on a
target
> > machine, a Win98 machine. I cannot run the DLL on my development
machine, a
> > win2K machine, because I take advantage of being able to directly access
> > hardware (I do plan on upgrading the DLL to work with Win2K and XP later
but
> > I have to fix this first).
> >
> > Anyway, I was able to install VC on the target machine and was able to
> > catch an error that has been giving me grief. However, I can only see
the
> > code as disassembled. Is there a way I can trace the address in the
> > disassembled code to the correcponding call in the C code?
> >
>
> You should produce debug information for the DLL, and make it available
> on the target system.
>
> If you are debugging a Debug build with default settings, you should
already have
> the debug information in two .PDB files in the output directory
(yourdll.pdb and vc60.pdb
> (assuming that you use VC60)).
> Copy these files to the target and put them into the same directory as the
DLL.
> Also copy source files to the target. Then you can debug the DLL, and the
debugger
> should be able to find and load debug information for it.
>
> After you have reproduced the problem, you might already be able to see
> the offending source. If you still see disassembly, do R-Click | Go To
Source
> to see the source file. You might be asked for the path to the source
file.
>
> If you are debugging a Release build, produce debug information with the
following
> compiler and linker options:
> Compiler: /Zi
> Linker: /debug /debugtype:cv /pdb:yourdll.pdb /pdbtype:con /opt:ref
> (all these options can be configured in the IDE, see documentation for the
options)
>
> If something still does not work, tell us - there are ways to troubleshoot
it.
>
> If you cannot reproduce the problem anymore but remember the faulting
address,
> there are also ways to recover the source file/line.
>
> Regards,
> Oleg
>
>
>
>
>
>

Relevant Pages

  • Re: 2.6.25-rc2 System no longer powers off after suspend-to-disk. Screen becomes green.
    ... doesn't even take the target state into account at all. ... usage - for given target system sleep state. ... real issue here is that the interface is really rather mis-designed) ...
    (Linux-Kernel)
  • ESS Flash Tasks
    ... I am having an issue with a flash process that I am unable to identify.. ... My target server has the same two volume groups ... Then varyon and mount the filesystems on both the source and target ... during the varyonvg for the target system) and the data itself is fine ...
    (AIX-L)
  • Re: How to create a component to set the windows directory
    ... My target system boot on the C drive and Windows is stored ... It`s work fine on my target system. ... the "Target Device Settings", ...
    (microsoft.public.windowsxp.embedded)
  • Re: How to change text color
    ... >text color in target system. ... Where to verify whether my BSP is ... >supporting different text color or not? ...
    (comp.os.vxworks)
  • Re: Debugger is "Unattached"!
    ... I have a target system on Vmware and may PC as the Host. ... How can I debug my VxWorks? ... When you need to debug certain task, ...
    (comp.os.vxworks)