Here's a repost of an email I sent that didnt seem to get through:
I lost track of the original problem, but are you stepping into a shared library
or static library? If you want to step into a static library, then just as an
experiment try this to see if the same thing happens here: try rebuilding
StartupCode.lib with debugging information (inside your Palm OS 3.5 Support
folder, look for the project StartupCode.mcp, Enable Debugger, turn off all
optimizations and then rebuild it. An Obj subfolder will be created at the same
level as StartupCode.mcp. Remove StartupCode.lib from your project, and add the
StartupCode.lib from the Obj folder.) Debug your app. When the debugger comes
up, look at the stack crawl and click on __Startup__. If you see source code
then you have just viewed the code for StartupCode.lib, debug build. Let me know
if this works.
-- jkl
----- Original Message -----
From: "Chris Percival" <[EMAIL PROTECTED]>
Newsgroups: palm-dev-forum
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Friday, March 02, 2001 7:26 AM
Subject: Re: Stepping into library code
> Thanks Terry, I think this was the conclusion I was comming to. There is no
> 'nice' way to do it... I hope this gets addressed in some later versions of
> palm/codewarrior stuff.
>
> --
> Chris Percival
> www.interaxis.co.uk
>
> Chris Percival <[EMAIL PROTECTED]> wrote in message
> news:40986@palm-dev-forum...
> >
> > Ok, I have dragged the library MCP file into the main project. I have
> > expanded the library targets in the main project and selected which
> library
> > target I want to link against (and noticed that it automatically added the
> > required lib files to the project). However I still can't step into
> library
> > source code, only assembler. Do I need to add the library project source
> to
> > the main project? I tried this and this causes all sorts of problems,
> like
> > for instance if I have a library project source file with the same name as
> a
> > source file in the main project it doesn't let me add it, meaning I can't
> > build and debug. Doing this would also cause lots of version control
> > headaches, and kind of defeats the exersise of building a library in a
> > separate project in the first place. There has to be an easier way?
> >
> > --
> > Chris Percival
> > www.interaxis.co.uk
> >
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
