[Gc] Status of gc on Mac OS X running on intel proc ?
hans.boehm at hp.com
Thu Sep 28 14:02:01 PDT 2006
Thanks. It looks like there are two issues here:
1) Thread_get_state usually fails in gctest. The calling code is at
around line 100 in darwin_stop_world.c. It would be good to see if you
can get more information from the return code or anything else to figure
out why this is happening. I think this is the most serious problem.
2) It looks like test_cpp is invoking the system free when it shouldn't.
The next step here would be to look at the stack trace when the error
message is printed to see where the free call is coming from. This
looks like a problem that's specific to the gc_cpp.h C++ interface,
probably related to replacing ::new and friends.
It looks like single-threaded C applications probably work, at least if
you build without thread support.
> -----Original Message-----
> From: gc-bounces at napali.hpl.hp.com
> [mailto:gc-bounces at napali.hpl.hp.com] On Behalf Of Renaud Blanch
> Sent: Thursday, September 28, 2006 12:22 AM
> To: gc at napali.hpl.hp.com
> Subject: [Gc] Status of gc on Mac OS X running on intel proc ?
> I was successfully using gc6.8 on a PPC PowerBook and on a
> dual G5 Mac running Mac OS X version 10.4.
> I switched to an Intel dual core MacBook Pro a few weeks ago.
> Basic make check reports failures on Mac OS X while it works
> fine on the same machine running linux (ubuntu with a SMP kernel).
> Has anybody reported similar problems or conversely reported
> success in using the gc on intel (dual core) based machine
> running Mac OS X ?
> In case it helps, you will find below the configure and make
> check logs for gc6.8 & gc7.0alpha7 for both linux & Mac OS X runs.
> I will happily collaborate with people motivated to provide
> patch to the gc in order to make it work for intel macs.
> If some body can point me in the right direction, and give me
> some hints, I am also motivated to contribute !
More information about the Gc