As spidermonkey-1.8.5 is very much not compatible with earlier versions of spidermonkey, and migrating to the new API as per upstream documentation is not always enough to provide something that works at runtime, it would be very much appreciated if we could install a development / debug build of spidermonkey-1.8.5 in order to aid in the mirgration process of packages depending on it. Reproducible: Sometimes Steps to Reproduce: 1. install spidermonkey-1.8.5 2. migrate your application to support JS_VERSION 185 without any compile warnings 3. run your application and watch it segfault on something within libmozjs.so
What configure option is needed to improve backtraces? If none exists, the USE flag is not needed but people needs to follow, as always: http://www.gentoo.org/proj/en/qa/backtraces.xml
Well, adding --enable-debug turns on a whole ton of "assert" logic, which helps significantly with the whole application debugging process. Without it one just ends up with segfaults coming from deep within the jsapi code. I'm not sure if that answers your question??
So is there a decision on this one? Or should i just plan to overlay the ebuild on my development systems?
(In reply to comment #3) > So is there a decision on this one? Or should i just plan to overlay the > ebuild on my development systems? We are working on adding the support, will be avaliable later tonight.
Thanks for reporting, bugs have been addressed if problem persists do not hesitate to reopen.
