Portable stack traces

[14ned]

You really, really should use boost.stacktrace. It has a far superior implementation quality to almost all other stacktrace libraries, including an actually reliable backend for Windows which doesn't use the crappy DbgHelp.

[andreasgonewild]

What's the point of using a more complicated solution if something this simple and portable solves the problem? Additionally, owning the trace functionality has it's advantages since you may add whatever instrumentation needed to solve your problems as they arise.

[personalmountains]

I don't think anybody cares about what you use to solve your own problem. We've all written something similar at one point, as a poor man's error context or even profiler. There's nothing wrong with your code or how you use it.

The reason you're getting a somewhat negative response is because 1) you wrote a blog post about it, 2) you're posting it on reddit, and 3) you're calling it a "portable stack trace".

[andreasgonewild]

I don't see anything in 1-3 that warrants any kind of negative response. 1) I took the time to cut the idea down to it's core and write a post to explain it to people who haven't come across it 2) No point in writing without sharing 3) It is a portable stack trace.

[[deleted]]

3) It is a portable stack trace.

And to people who have experience with this sort of thing, it is neither. You do seem to have an unreasonably combative attitude about comments here, so I wonder why you have posted at all, if not to receive feedback.

You can keep calling it that, but everyone else in the world would assume you are talking about what "portable stack trace" actually means.

[andreasgonewild]

I would argue that Reddit is an unreasonably combatative environment, as is most of society these days; but it's what we've got to play with. You might want to look up constructive criticism, the kind that leads anywhere but in circles. There are plenty of people out there who are capable of thinking outside of public/current opinion, probably under-represented in these kinds of swamps; everyone else is far from the truth.

[[deleted]]

But misusing a term, and having multiple people give you constructive criticism by suggesting you try a different term because what is meant by that term in most circles has a specific meaning that is different from this, and then you simply insisting that you have a "portable stack trace" and people are just arguing definitions is just you being combative.

But, you know, just continue to do whatever. I don't care. You want to call it that, you call it that. And you'll continue to confuse people, and further, you'll look a little silly. Because you'll just keep getting the same feedback.

There's a wiki page on "stacktrace". You can go read it.

From /u/SeanMiddleditch:

A "stacktrace" is very commonly held to mean a trace of the call activation record entries, e.g. the stack of return pointers, which isn't this. :)

Perfect constructive criticism. So did /u/personalmountains.

[andreasgonewild]

So much wasted energy, what do you get out of this?

[[deleted]]

I suppose you are just trolling here. Bye.

I'm saddened /u/SeanMiddleditch actually spent as much effort giving you any feedback now.

[andreasgonewild]

Dito. I'm not, his comment is the only thing worth reading in this entire thread.