devkitPro

I unit tested it a bit so it may not work every time, but I created something to start with: int backtrace (void **buffer, int size) { int depth; u32 stackptr, lr, *addr; // get link register asm volatile ("mflr %0" : "=r"(lr)); // link register is assigned to depth[0] buffer[0] = (void *) (lr - 4 ...

Hi, I was wondering, if an exception occurs the stack backtrace is shown, and code locations can be looked up with addr2line. According to GNU C++, the same can be achieved using the backtrace function that is defined in execinfo.h. This file doesn't seem to be available in devkitPPC. My question is ...

Would it be possible to run a ppc version of gdb on the wii itself? Or would that suffer from the same interrupt issues?

reg,

Danny

Why don't you use Eclipse+CDT and either Wiiclipse plugin or configure it to run 'make target' in msys.

Eclipse will give you stuff such as code completion, finding declarations/references, refactoring as a bonus too.

Thanks for your insight! You really know the good stuff. And it completely makes sense to me that your goals with devkit ppc are a bit broader than 'fighting' Nintendo;) I guessed that it would be due some OS stuff, but 12MB still seems a lot. It would be nice if some redundant services could be ...

Hi,

I've been wondering this for about 3 years now. The Wii has 64MB of DRAM available. Why is it that only 52MB of that can be allocated? Does anyone know a way to work around it?

reg,

Danny

Nice to see people answering their own questions:)

Do you also emulate a 60/50Hz display interrupt? In the days computers didn't have high precision timers yet programs could use display interupts for timing. But I'm sure you are aware of that.

I think I download devkit in april or perhaps may this year but for me lighting is working correctly. Note that GXSetChanCtrl(GX_COLOR0A0, GX_ENABLE, GX_SRC_REG, GX_SRC_REG, GX_LIGHT0, GX_DF_CLAMP, GX_AF_NONE); creates an on/off behaviour on actual hardware. To get actual cosine attenuation you have ...

Thanks! Though I'm a bit confused how to compute the normal mtx. I'd say modelview minus the translation. I'm not sure, but I suppose that can be achieved by applying mtxinverse, mtxtranspose and a mtx inverse. But doing that makes the bumps hard to see. Any ideas? Anyway, I'm implementing this and ...

Is anyone working on a libogc GXReadBoundingBox yet? And, say thay you draw a poly which completely fails the z test (the polygon is behind others and has no visible pixels), does it leaves the bounding box unaffected?

reg,

DRS