Matt, that's an awesome (and generous) offer. Find someone near by and get them to give you a pat on the back or a big high five.
I'm in Ottawa, Canada for reference, but while I do really want to get this working - I'm pretty sure I can source a G4 locally. If that fails and the priority of this problem grows, I'll reach out. Thanks On Wednesday, October 16, 2013 9:43:48 AM UTC-4, Matt Sergeant wrote: > > If you really want to get this working, I could donate my G4 MacBook Pro > to you. Email me off-list if you're interested. No idea where you're > located so delivery might be an issue. > > > On Wed, Oct 16, 2013 at 9:19 AM, Andrew Low <[email protected]<javascript:> > > wrote: > >> Chasing this is a side-project, I've got plenty of other stuff I'm >> working on too :) >> >> The main reason that this is interesting is that it might help me >> resolve: >> https://github.com/**andrewlow/v8ppc/issues/93<https://github.com/andrewlow/v8ppc/issues/93> >> -> >> but only if I can wrangle up some local hardware. Working over the wire is >> ok, but very very slow. These types of problems require a lot of iterations. >> >> Thanks for the details on your iBook. One of the guys here has an old G4 >> we can try out, but we need to install Linux on it. >> >> The trace is informative as well. It shows that "lots" of code is >> running, but you hit something specific causing a problem. This is not >> likely an issue with the Node code, but something in V8 (the JS runtime >> engine used by Node). >> >> If you want to tinker - build the V8 code and run it. >> >> git clone https://github.com/andrewlow/v8ppc.git >> cd v8ppc >> make dependencies >> make ppc >> >> Then run the resulting d8 shell. >> >> ./out/ppc.debug/d8 >> >> If that works, you can try some simple JS code (either type it in to the >> shell, or pass a foo.js file in on the command line). >> >> To run the V8 test suite, try: >> >> tools/run-tests.py -j 12 --progress=dots --no-presubmit >> --arch-and-mode=ppc.debug >> >> When you have a crash case - running the scenario under gdb and capturing >> some info from there will be helpful. >> >> gdb out/ppc.debug/d8 >> >> inside gdb: >> r <optional command line args> >> ... it crashes.. >> bt <- generates a back trace, likely corrupted >> x/20i $pc-16 <- dump instructions around the crash location >> i r <- dump registers >> >> That data will help isolate the issue. >> >> On Wednesday, October 16, 2013 7:10:37 AM UTC-4, Carlos Arija wrote: >>> >>> First of all, please do not put much time in this problem. It is just a >>> test. >>> Any way, here are the iBook G4 specs, if they are of any use to you. >>> And if I could be of any help in your project, just tell me. >>> >>> /etc/issue >>> Debian GNU/Linux 7 \n \l >>> >>> /proc/cpuinfo >>> processor : 0 >>> cpu : 7447A, altivec supported >>> clock : 1199.999000MHz >>> revision : 1.2 (pvr 8003 0102) >>> bogomips : 73.72 >>> timebase : 18432000 >>> platform : PowerMac >>> model : PowerBook6,5 >>> machine : PowerBook6,5 >>> motherboard : PowerBook6,5 MacRISC3 Power Macintosh >>> detected as : 287 (iBook G4) >>> pmac flags : 0000001b >>> L2 cache : 512K unified >>> pmac-generation : NewWorld >>> Memory : 1280 MB >>> >>> Attachment: result of ./node -trace, until the program crashed with an >>> "illegal instruction" >>> >>> >>> El martes, 15 de octubre de 2013 22:15:28 UTC+2, Andrew Low escribió: >>>> >>>> I've got some good news and some bad news. >>>> >>>> Bad news - I can't replicate your problem. >>>> >>>> Good news - I was able to dig up an old PowerMac running Ubuntu. >>>> >>>> $ cat /etc/issue >>>> Ubuntu 10.04.4 LTS \n \l >>>> >>>> Unfortunately it appears to be a G5, not a G4. >>>> >>>> $ cat /proc/cpuinfo >>>> processor : 0 >>>> cpu : PPC970FX, altivec supported >>>> clock : 1800.000000MHz >>>> revision : 3.0 (pvr 003c 0300) >>>> >>>> processor : 1 >>>> cpu : PPC970FX, altivec supported >>>> clock : 1800.000000MHz >>>> revision : 3.0 (pvr 003c 0300) >>>> >>>> timebase : 33333333 >>>> platform : PowerMac >>>> model : PowerMac7,3 >>>> machine : PowerMac7,3 >>>> motherboard : PowerMac7,3 MacRISC4 Power Macintosh >>>> detected as : 336 (PowerMac G5) >>>> pmac flags : 00000000 >>>> L2 cache : 512K unified >>>> pmac-generation : NewWorld >>>> >>>> FWIW - v8 seems to bootstrap just fine >>>> >>>> $ ./out/ppc.debug/d8 >>>> V8 version 3.14.5 (candidate) [console: dumb] >>>> d8> 3+4 >>>> 7 >>>> d8> >>>> >>>> >>>> >>>> -- >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to [email protected]<javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
