Re: No source visible in debugger

In article <2005092610064716807%danny@metadmacom>,
Danny at META/DMA <danny@xxxxxxxxxxx> wrote:

I don't think 9.6 changed anything with debugging. It seems to be
something on your end. Make sure you aren't following some old file.
(that is make sure the file you are debugging is the only one and there
isn't an older version in the trash or somewhere). Also be sure that
optimizations are not on in your plugin.

Ron

>I've been running into the exact same problem with debugging an Adobe
>After Effects plugin -- that is, I can only see disassembly rather than
>source code in the debugging window. I'm almost positive that this is a
>CW 9.6 problem. It worked fine in 9.5, and I haven't touched my project
>until after updating to 9.6, when I could no longer debug. It's a very
>small project, so I don't think I've hit any kind of header limit.
>Unfortunately, none of the tricks listed below help at all. My only
>solution seems to be to revert to CW 9.5 (or XCode), unless anyone has
>any other ideas. Anyone?
>
>Thanks,
>
>Danny Rosenberg
>META/DMA
>
>On 2005-08-09 11:40:56 -0700, "George Touchstone"
><GroupPosts@xxxxxxxxxxxxx> said:
>
>> After a further email exchange with mwRon and trying a few more things,
>> I've come up with the following observations and a restatement of Ron's
>> suggestions.
>>
>> MW says no-one at Adobe is complaining about this, but I have heard
>> from at least one other InDesign plugin developer reporting the same
>> problem and asking if I have further insight. That query prompted this
>> update to this NewsGroup thread.
>>
>> I believe the c++ headers in the InDesign SDK create massive numbers of
>> symbols which in turn exceeds what MW thought was at the time a
>> reasonable limit. Which is in a way an object lesson to all of us about
>> making assumptions about "reasonable limits" in our code.
>>
>> I am able to debug the sample plugins provided by Adobe in the SDK, and
>> I'm able to debug the smaller modules in my own project. However, in
>> some cases I've combined code from several sample plugins. This results
>> in more header includes that are typically found in the sample plugins.
>> It is these modules that appear only in assemply language in the
>> debugger.
>>
>> I'm hoping CW10 addresses this.
>>
>> How to deal with it for now:
>> You have to very selectively enable debugging on a few modules.
>> You have to minimize how many headers you include.
>> Then you have to "reset" the debugger from time to time when it goes
>> over the limit.
>>
>> How to "reset" the IDE/Debugger:
>>
>> In Project settings, under Linker, be sure "Generate Sym File" is on
>>
>> Be sure that the debug column is set for the files you want to debug
>>
>> In IDE Preferences, Debugger, Global Settings:
>> Purge the debugger cache
>>
>> Remove object code
>> Trash the sym file
>> Empty the trash
>>
>> If that doesn't work, something more dramatic:
>> Go to
>> <YourOSXBootVol>/Users/<YourUserName>/Library/Preferences/Metrowerks,
>> Delete "CW IDE 5.5 Prefs" (actual version may be newer)
>> Delete "CW Debugging Cache"
>>
>> Good luck, and thanks again to Ron for his help,
>>
>> George Touchstone
>> Sacramento Software Works
>> www.SacraSoft.com
>> George at SacraSoft dot com
>
>

--
CodeWarrior Community Forum is a free online resource for developers
to discuss CodeWarrior topics with other users and our staff
-- http://www.codewarrior.com/community --

Ron Liechty - ron.liechty@xxxxxxxxxxxxx - http://www.codewarrior.com
.

Relevant Pages

  • Re: No source visible in debugger
    ... I've been running into the exact same problem with debugging an Adobe After Effects plugin -- that is, I can only see disassembly rather than source code in the debugging window. ... some cases I've combined code from several sample plugins. ...
    (comp.sys.mac.programmer.codewarrior)
  • Re: Office or InDesign breaks VS 2005 debugging?
    ... Given tha I was using and debugging the sub-projects in this solution before ... some getting used to) and the debug symbols for the child project are no ...
    (microsoft.public.vsnet.debugging)
  • Re: Cant Debug COM Interface
    ... When I start to debug the application the DLL is ... a com client in vb.net which is referencing the interface of the COM Server ... If I use this application as Host application I can debug without ... For debugging I can start the ...
    (microsoft.public.vsnet.debugging)
  • Re: C++ Workable Mainframe Debuggers
    ... you have to be able to read assembler to do ... IBM Debug Tool for z/OS is available. ... You can license Debug Tool as MLC or, in the form of the Debug Tool ... For graphical debugging use Rational Developer for System z (or ...
    (bit.listserv.ibm-main)
  • Re: Need help with my logic
    ... Hand Execution ... This will save you a lot of time when you write (and debug) large programs. ... In each method put at least one debugging statement at the head of a method that accepts information to show the arguments: ...
    (comp.lang.java.programmer)