I assume the fix would be to install an EXC_BAD_ACCESS
handler after kicking off the app event loop. That would
make sure that Carbon never saw it.
But I don't know how to do that.
I don't have a 10.5 mac to see if this is moot with the changes to
CrashReporter.app.
mach/mach.h has thread_
On Jun 28, 2008, at 6:17 PM, Anant Narayanan wrote:
Running 9vx with the -F flag makes that error go away (tried on
10.5.3)
That helped, but I get the spurious error.
Hi,
First off, 9vx is incredible! Thanks Russ and Bryan :)
When I start 9vx, I get the following messages dumped to terminal
repeatedly and the app hangs:
cpu10: runproc spurious wakeup
idlehands spurious wakeup
I got the new 0.11 source to build, but run into a similar error:
cpu3: runproc
Russ,
Great work with 9vx. I haven't played around with it too much, but I
did successfully build your native gui code cleanup.
When I start 9vx, I get the following messages dumped to terminal
repeatedly and the app hangs:
cpu10: runproc spurious wakeup
idlehands spurious wakeup
Perhaps this ha
Running the new native 9vx (which I was almost done doing myself, had
it not been for that missing file):
The process has forked and you cannot use this CoreFoundation
functionality safely. You MUST exec().
Break on
__THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALI
> Unfortunately, it seems to have one problem: the
> Carbon app event loop appears to install its own
> handler for EXC_BAD_ACCESS, the Mach equivalent
It looks like this might be fixed in 10.5, according to
http://developer.apple.com/technotes/tn2004/tn2123.html#SECLIMITATIONS
Of course, if you
The 9vx 0.11 source code includes OS X gui code,
a severely cleaned-up version of the drawterm code.
It is not built by default, but you can build it by using
make 9vx/9vx PLAN9GUI=osx
Unfortunately, it seems to have one problem: the
Carbon app event loop appears to install its own
handl
