Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Programming / CodeWarrior / July 2003



Tip: Looking for answers? Try searching our database.

yet another shared library debugging problem post

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Micah - 30 Jul 2003 05:47 GMT
I swear I spent many hours going through all the newsgroups and
following all the directions to debugging a shared library.  I know
Ron has posted about this topic many times, but I simply cannot debug
my shared library using 8.3, OS 10.2.6.

I have opened the xSYM file, set my breakpoints, and launched the
application from the finder with the control key down (since
contextual menu pops up, I assume this means I should select "open"
and keep the control key down).  Alas, the application starts up
without breaking in my library when it loads.  Subsequent interaction
which I know calls my library also fails to cause the breakpoints to
hit.

I HAD CW 8.0, updated to 8.2, then 8.3.  I then updated my dev tools
to the suggested December 2002.  I even re-installed 8.3 in case the
order matters... I even trashed my MW prefs just for good measure.

Attempting to click the run in debugger button from the project window
causes my host apps "main thread" window to appear, but spinning beach
ball forever after that.

Attempting to attach to the app's process AFTER it has called my
library also causes a never ending spinning beach ball.

I must be missing some small crucial step.  Please help and thank you,

Micah
David Phillip Oster - 30 Jul 2003 06:54 GMT
> I must be missing some small crucial step.  Please help and thank you,

Have you considered adding an explicit call to:

Debugger();

early in some routine of your shared library that is called early by
your app?

This is a trick I've used in the past to get the debugger's attention.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.