[Bug 470696] Review Request: rubygem-passenger - Passenger Ruby on Rails deployment system

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=470696

--- Comment #97 from Hongli Lai <honglilai at gmail.com> 2011-09-28 14:03:16 EDT ---
Hi Brett. If you can get the changes bundled in Boost then what we can do is
adding an option to disable compiling against the bundled Boost, and instead
compile against the system Boost. We'll still want to continue bundling Boost
for the sake of platforms on which installing Boost is a hassle (e.g. OS X),
but I believe adding such a compile option should solve your issue as well.

I do not mind it if the API that the Boost folks develop is slightly different
than ours.

It should be noted that our backtrace support is not automatic. It relies on
the user manually specifying backtrace points with TRACE_POINT() macros. It's
documented here:
https://github.com/FooBarWidget/passenger/blob/master/ext/oxt/backtrace.hpp
The backtrace system is built in such a way that it can be integrated with
oxt::thread. oxt::thread is like boost::thread but also registers each thread
on a global thread list, each of which has its own thread-local backtrace list.
This way, one can obtain the backtraces of all threads during runtime.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.