I have this large application written in CW PowerPlant.
It runs well on the PPC -- don't know about intel-based macs.
After upgrading from Tiger to Leopard, the app got unstable
(and, FWIW, I have the impression that the Leopard upgrade
from 10.5 to 10.5.1 increased the unstability a lot).
Naturally, I opened up the CodeWarrior project to have a look
at what the trouble might be. Long story short:
On Leopard (10.5 or 10.5.1) the CW project will not build,
for a variety of problems having to do with header files not found.
The project builds OK under (any version of) Tiger,
so one could debug on Tiger, except that the app is stable on Tiger,
so there is nothing to debug there; and since the project won't build
on Leopard, debugging on Leopard is not possible.
I desparately need help or hints. I've searched the web
many times, many keywords; a post by John Brownie, 1 Nov '07
on carbon-dev (unresolved) is all I can find.
Has anyone else seen this problem?
Is my project the last extant CodeWarrior project?
(I have two long-running conversion projects underway,
one to port to Carbon on Xcode; one a complete rewrite in Cocoa,
but neither is close to completion)
More details:
I've investigated the old fashioned way, iterating (a) and (b):
(a) Launch Tiger, add some "trace code", compile and build, then (b):
(b) Launch Leopard, run the app, examine the trace output, then (a).
About half the time, the crash occurs in the PowerPlant function
LArray::PeekItem(long index, void* buffer).
The code there warns that the buffer should be long enough.
For the curious, two dump examples appear further below.
Here is a quick way to see the problem with headers:
Launch CodeWarrior v10 (the final version);
Command-shift-N to create a project:
select "Mac OS PowerPlant Stationery"
then select "Mac OS X Mach-O",
then select "Advanced".
On Tiger, the resulting sample project builds and runs.
On Leopard, there are warnings and errors stemming from deep
within CarbonCore, e.g. in signal.h, ppc/vmparam.h,
sys/resource.h, sys/fctl.h, unistd.h, ColorSynch.h, etc.
It seems curious to me than BOTH CodeWarrior,
and my app built on CodeWarrior, should fail to move to Leopard.
Codewarror uses system headers in 'Developer' -- FWIW,
I moved directly from Xcode 2.4.1 to Xcode 3.0,
bypassing Xcode 2.5. But the app, once built,
is constant and doesn't rely on "current" headers. Yes?
Any hints, clues, references, or similar experiences?
-- James
Thread 0 Crashed:
0 0x000b6840 LArray::PeekItem(long, void*) const + 100
1 0x000b512c LArray::FetchItemAt(long, void*) const + 80
2 0x000b71d4 LArrayIterator::Current(void*) + 72
3 0x000b7234 LArrayIterator::Next(void*) + 48
4 0x0012acbc TArrayIterator<LDocument*>::Next(LDocument*&) + 28
5 0x000b0da0 LDocument::FindByFileSpec(FSSpec const&) + 116
Thread 0 Crashed:
0 0x000b6700 LArray::PeekItem(long, void*) const + 100
1 0x000b5078 LArray::FetchItemAt(long, void*) const + 80
2 0x000b7094 LArrayIterator::Current(void*) + 72
3 0x000b70f4 LArrayIterator::Next(void*) + 48
4 0x0002272c StoxFile::FindDocumentByWindow(LWindow*) + 100
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
