Portable stack trace mechanism?
From the evidence I can conclude that it never made it in, but the
I've written this code several times and thought boost might have something. No, it doesn't, but I found this old bit thread: http://lists.boost.org/Archives/boost/2010/10/172303.php thread gives no indication as to why. I don't want to resurrect something that's already been fully hashed and excluded, but if it never made it in simply because nobody carried the torch forward, perhaps I could be the new bearer.
On 10/17/2011 1:26 PM, Chris Cleeland wrote:
I've written this code several times and thought boost might have something. No, it doesn't, but I found this old bit thread:
http://lists.boost.org/Archives/boost/2010/10/172303.php
From the evidence I can conclude that it never made it in, but the thread gives no indication as to why. I don't want to resurrect something that's already been fully hashed and excluded, but if it never made it in simply because nobody carried the torch forward, perhaps I could be the new bearer.
A portable stack trace mechanism that would be able to show file/line would be great. But without the file/line information it would be much less useful.
A portable stack trace mechanism that would be able to show file/line would be great. But without the file/line information it would be much less useful.
I second this!
In some cases, for file/line information you have to either link with libraries such as libbfd on Linux (and you get to depend on external & platform dependent libraries); either you have to delve into the intricacies of file formats yourself (elf, dwarf, etc). Regards, Aurelian
On 1:59 PM, Chris Cleeland wrote:
I've written this code several times and thought boost might have something. No, it doesn't, but I found this old bit thread:
http://lists.boost.org/Archives/boost/2010/10/172303.php
From the evidence I can conclude that it never made it in, but the thread gives no indication as to why. I don't want to resurrect something that's already been fully hashed and excluded, but if it never made it in simply because nobody carried the torch forward, perhaps I could be the new bearer.
I think that would be cool. That thread was started by Artyom, author of Boost.Locale. I copied him on this reply.
The code runs as a part of the CppCMS project (under namespace booster). I hadn't pushed it forward due to several reasons: 1. I had no much time to work on it (create jam files etc) 2. I was not sure about how deep the interest was and what it would require. It works fine on Linux, Windows with MSVC, Solaris and AFAIR Mac OS X. Artyom Beilis -------------- CppCMS - C++ Web Framework: http://cppcms.sf.net/ CppDB - C++ SQL Connectivity: http://cppcms.sf.net/sql/cppdb/ ----- Original Message -----
From: Jim Bell
To: boost-users@lists.boost.org Cc: Chris Cleeland ; Artyom Sent: Sunday, October 23, 2011 8:26 PM Subject: Re: [Boost-users] Portable stack trace mechanism? On 1:59 PM, Chris Cleeland wrote:
I've written this code several times and thought boost might have something. No, it doesn't, but I found this old bit thread:
http://lists.boost.org/Archives/boost/2010/10/172303.php
From the evidence I can conclude that it never made it in, but the thread gives no indication as to why. I don't want to resurrect something that's already been fully hashed and excluded, but if it never made it in simply because nobody carried the torch forward, perhaps I could be the new bearer.
I think that would be cool. That thread was started by Artyom, author of Boost.Locale. I copied him on this reply.
participants (6)
-
Artyom Beilis
-
Aurelian Melinte
-
Chris Cleeland
-
Diederick C. Niehorster
-
Edward Diener
-
Jim Bell