Re: [boost] Is there interest in a collection of call stack utilities?
Hello, To follow up on the discussion https://groups.google.com/forum/#!topic/boost-developers-archive/PSwTBEEe0Ao I was not clear if there is interest for it or not. I went ahead and the first cut of the code is now at https://github.com/melintea/Boost-Call_stack Please feel free to take a look and comment. Regards, Aurelian
On Nov 16, 2013, at 6:55 PM, Aurelian Melinte <ame01@gmx.net> wrote:
To follow up on the discussion https://groups.google.com/forum/#!topic/boost-developers-archive/PSwTBEEe0Ao
I was not clear if there is interest for it or not.
From that discussion, I'd say there was obvious interest in such functionality.
I went ahead and the first cut of the code is now at https://github.com/melintea/Boost-Call_stack
Please feel free to take a look and comment.
Did you address any of the criticisms of your first version or design? It isn't fair to ask people to look again and find the same issues. How does what you've done compare to Artyom Beilis' library? ___ Rob (Sent from my portable computation engine)
Did you address any of the criticisms of your first version or design? It isn't fair to ask people to look again and find the same issues.
How does what you've done compare to Artyom Beilis' library?
I believe I did addressed all except Artyom's suggestions to use another API. This is code that uses Boost constructs and useable by older compilers. You may find this library a bit more flexible and extendable than Artyom's library but since it offers the same core functionality, I think it is ultimately a matter of choice. Regards, Aurelian
On 17-11-2013 00:55, Aurelian Melinte wrote:
Hello,
To follow up on the discussion https://groups.google.com/forum/#!topic/boost-developers-archive/PSwTBEEe0Ao
I was not clear if there is interest for it or not.
Haven't followed the other thread, but I think there will be great interest in such a library. regards -Thorsten
On Mon, Nov 18, 2013 at 4:27 AM, Thorsten Ottosen < thorsten.ottosen@dezide.com> wrote:
On 17-11-2013 00:55, Aurelian Melinte wrote:
I was not clear if there is interest for it or not.
Haven't followed the other thread, but I think there will be great interest in such a library.
I second that. I have not followed the discussion either and have no particular opinion on the issues discussed in it. But one this is for sure, I would have great interest in such a library, and I would imagine many others would too. The "traced_exception" example is particularly compelling. regards, Sven Mikael Persson, M.Sc.(Tech.)
Aurelian Melinte <ame01 <at> gmx.net> writes:
I was not clear if there is interest for it or not. I went ahead and the first cut of the code is now at https://github.com/melintea/Boost- Call_stack
Boost.Test might be interested in using something like this. I noticed though this is header only solution. I do not think this would be acceptable to me (given all the lower level system details one need to have inside of the implementation). Otherwise looks interesting. Gennadiy
Boost.Test might be interested in using something like this. I noticed though this is header only solution. I do not think this would be acceptable to me (given all the lower level system details one need to have inside of the implementation). Otherwise looks interesting.
I have noted the concern. This is an easy change. Thanks, Aurelian
2013/11/17 Aurelian Melinte <ame01@gmx.net>
Hello,
To follow up on the discussion https://groups.google.com/ forum/#!topic/boost-developers-archive/PSwTBEEe0Ao
I was not clear if there is interest for it or not. I went ahead and the first cut of the code is now at https://github.com/melintea/ Boost-Call_stack
Please feel free to take a look and comment.
There's definitely an interest in such library. Looking through the docs I did not find the requirements for a resulting binary: can it be stripped? can it work without pdb file and sources? Will the stack detalization change depending on existance of pdb/debug info? -- Best regards, Antony Polukhin
participants (6)
-
Antony Polukhin -
Aurelian Melinte -
Gennadiy Rozental -
Mikael Persson -
Rob Stewart -
Thorsten Ottosen