Getting a stack trace in C++ exceptions

Question

The fact a stack/function trace is supplied in Java/C# exceptions is really useful. Is there a handy way to do this in C++ or would I have to bake extra data into every method/function?

Duplicate??: http://stackoverflow.com/questions/3222890/call-stack-for-exceptions-in-c — bcsanches, Dec 30 '10 at 12:02

score 1 · Answer 1 · edited May 23 '17 at 10:33

1

Most debuggers can be set up to pause your program each time an exception is thrown (either any exception or an exception for which there's no handler) so that you can obserevr a call stack.

Also if your code only throws exceptions of classes you control you can put code for dumping the call stack in those classes constructors.

edited May 23 '17 at 10:33

Community

1
1

answered Dec 30 '10 at 11:28

sharptooth

167,383
100
513
979

This is for logging exceptions in the wild, not during debugging. – Mr. Boy Dec 30 '10 at 11:31
@John: The second paragraph is about that - actually the whole question I link to is about that. – sharptooth Dec 30 '10 at 11:41
I think the question is then "what code should be in the constructors of exception classes to get a stack trace"? – Mr. Boy Dec 30 '10 at 11:43
@John: That will be platform-dependent. – sharptooth Dec 30 '10 at 11:45

score 0 · Answer 2 · answered Dec 30 '10 at 11:44

0

If you are considering adding metdata to your exceptions, You may consider using boost exception handling . boost::exception allows adding information to an exception after it has been thrown.

answered Dec 30 '10 at 11:44

Neera

1,577
8
10

score 0 · Answer 3 · answered Dec 30 '10 at 11:52

Some OS APIs provide for stack traces, I know that the Windows API has StackWalk64 or something like that that can do stack tracing.

However, if you can't depend on such a thing, then pretty much all you can do is either ship a debug build, or do it manually.

Getting a stack trace in C++ exceptions

3 Answers3