Re: Visual Studio 2005 - Stepping into Statically link libraries

Yes, my previous statement was wrong. I was also able to step into LIB
functions with EVC 4.0 where the EXE and LIB were separate projects. I guess
my memory failed me and I must have been thinking about cases of trying to
step into retail LIB files that didn't contain debug information. I'm looking
into VS and WM 5.0 now.

--
John Cramer
SOFTWARE DEVELOPMENT ENGINEER, Mobile Developer eXperience Team
Microsoft Corp.


This posting is provided "AS IS" with no warranties, and confers no rights.




"Byungho Lee" wrote:

> Actually I used to step into static library on eVC 4.0.
> Library was made on a different project using eVC4.0 on the same PC.
>
>
> "John Cramer [MSFT]" <JohnCramerMSFT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message news:5BEF4AF5-F038-4033-859B-5F120FA4C164@xxxxxxxxxxxxxxxx
> > I'm not absolutely sure, but I don't think you can step into statically
> > linked code from LIBs. I'm pretty sure I have never been able to, on any
> > platform, ever. If you use strings.exe to extract text from binary files,
> > you
> > won't find any references to the matching PDB file, as you will with .EXE
> > and
> > .DLL files, so that means there's no way for the debugger to find the
> > symbols
> > or sources.
> >
> > Since you seem to have the sources for the LIB files, you could debug by
> > compiling and linking the sources directly with your program, then split
> > it
> > out and make LIB files after everything works.
> >
> > --
> > John Cramer
> > SOFTWARE DEVELOPMENT ENGINEER, Mobile Developer eXperience Team
> > Microsoft Corp.
> >
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >
> >
> >
> >
> > "Constantine Zervos" wrote:
> >
> >> I am unable to step into functions that are part of a statically linked
> >> library.
> >>
> >> I am using Visual Studio 2005 beta2.050215-4400 (version 8.0.50215.44)
> >> and I
> >> am building native C++ code for the Pocket PC 2003 Second edition (both
> >> Target emulator and device exhibit the same problem)
> >>
> >> My solution consists of 4 projects 3 of which are statically linked
> >> libraries and the other is the Executable. When I try to debug the
> >> solution
> >> I am able step into all functions that are part of the project where the
> >> executable is generated but I can not step into any of the functions
> >> implemented in the other 3 projects (the libs). In reality I can not
> >> step
> >> into the functions when I am steeping through displaying the C-Source
> >> code.
> >> Stepping into a function (from the lib projects) results in just stepping
> >> over it. If I change the debugger to display the assemply code and I
> >> step
> >> into such a function I am able to follow the branch into the functions.
> >> Nevertheless there is no longer C-Source code association so this is not
> >> very useful.
> >>
> >> I thought there must be something wrong with my Solution & Project
> >> configurations but I tried all that seamed relevant with no luck. I
> >> tried
> >> explicitely adding the directories of the C++ source files for my lib
> >> projects into the "Debug Source Files" configuration of the Solution.
> >> That
> >> did not help. I also tried explicitely adding the full path to the *.pdb
> >> file under the tools->Options->Debugging->Symbols but that did not help
> >> either.
> >>
> >> At this point I am left wondering whehther this is a know issue with
> >> Visual
> >> Studio 2005 & Pocket PC. In other words has anyone been able to step
> >> into
> >> functions of libraries that are statically linked into a project which
> >> targets Pocket PC 2003? If yes what do you think I should try next? It
> >> is
> >> not obvious to me what I could be doing wrong.
> >>
> >> TIA,
> >>
> >> CZ
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: Where can I get DDK2000 for VSC++6.0?
    ... MS ships only Win2003/2000 DDK for .Net ... Where can I get the W2KDDK inc and lib files? ... "wnet" is simply the name used within the DDK to ...
    (microsoft.public.win32.programmer.kernel)
  • Re: linker error LNK2001: unresolved external symbol in VS2008 when building simple example
    ... When I put the lib name in Linker/Input/ ... why putting the path to the lib directory with .lib files ... It seems that your static library and executable are built with different CRT ... Is there any support service using vnc and dealing with VS problems? ...
    (microsoft.public.vc.ide_general)
  • Re: a flat distribution
    ... > int main (void) ... the lib files are all installed in the /usr/lib ... how can i point the compiler to the dir where it could seek for the lib ...
    (comp.lang.cpp)
  • Re: pe format in 2003
    ... Lib files are of course neither win32 modules nor dos modules. ...
    (microsoft.public.development.device.drivers)
  • Re: Getting started on the HP49g+
    ... either the original HP extable lib ... extable2 lib from http://www.hpcalc.org/details.php?id=3940. ... ask again if you have any problem installing libraries. ... compile the string with ASM (listed in the development lib menu, ...
    (comp.sys.hp48)