iSYM file corruption (reprise)
- From: Steve <root@xxxxxxxxx>
- Date: Tue, 26 Jul 2005 18:03:16 GMT
Hi,
BTW, before we start I know this is a bug with the x86 compiler and
Metrowerks don't support it anymore, but I thought I'd post this just for
information really. You never know, it might help someone....
Back in February I started a thread about our iSYM files becoming corrupted
and failing to load for debugging.
<http://groups.google.co.uk/group/comp.sys.mac.programmer.codewarrior/browse
_frm/thread/8e318cd0f09f0b59/631aac406c5a436b?lnk=st&q=isym+file+steve+folly
&rnum=1&hl=en#631aac406c5a436b>
Back then it was CW 9.3, OS X 10.3.7, x86 compiler, and we were getting the
error "Warning - this SYM file has some invalid or inconsistent data. the
debugger may show incorrect information"
Well, now its CW 9.5, OS X 10.4.2 (still the x86 compiler!), and the
situation hasn't changed. It been really painful debugging to say the least
- toggling the 'generate symbols' on and off until we get something that
builds! Until now...
The other day I started to investigate splitting our application into DLLs.
The first step was to get the application using the shared runtime library.
So I went through and changed all the projects used in the app to use the
Shared multi-threaded debug runtime configuration, added the stub .lib to
the main project.
So now the application is using MSL_All-DLL90_x86_D.dll and, to my utter
surprise I'm no longer getting any corrupted iSYM file problems. It's now
grown to 17.1MB and CodeWarrior doesn't even flinch.
Anyone care to explain? :-)
Still, I'm happy(ier) now, and so are the rest of the developers!
--
Regards,
Steve
"What if the Hokey Cokey really IS what it's all about?"
.
- Follow-Ups:
- Re: iSYM file corruption (reprise)
- From: MW Ron
- Re: iSYM file corruption (reprise)
- Prev by Date: Re: How to convert MAC paths to BSD (unix) paths?
- Next by Date: Re: linking gcc built libs
- Previous by thread: Codewarrior 9.5 and
- Next by thread: Re: iSYM file corruption (reprise)
- Index(es):