> > You wanna back up and try that again, Ben? :-) Poser captures the > > entire call stack on memory allocations and prints that out, > > something that's even shown in Jayan's posting (if possibly only in > > elided form). From Poser's release notes: > Eeek... OK, I've actually never used the leak detection... haven't > needed it yet. Sorry about not knowing its full abililties -- yes, I > misread the output. However, my technique may still be > useful. If POSE isn't showing a symbol, I wonder if the Macsbug > symbol is just too long for it, especially since mangled C++ names > for template-based types can get really large quickly.
Now imagine mangled C++ names for template-based types in namespaces. On a couple of occasions, I've gotten errors where I couldn't see what the class (much less the method) containing the error was because CodeWarrior cuts its error messages off after some reasonably-large- but-not-large-enough limit. Given that we can (with some pain) compile templated C++ classes in namespaces in CodeWarrior, are there any plans to increase the limit on error messages? Like, say, displaying the whole message? This would probably make the version 9 upgrade worth it to the company I work at... Later, Blake. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
