[fpc-devel] time for dumping stacktrace, when using dwarf.

"Vinzent Höfler" JeLlyFish.software at gmx.net
Tue Nov 10 21:32:33 CET 2009

Vincent Snijders <vsnijders at vodafonevast.nl>:

> Micha Nelissen schreef:
> > 
> > Allocating that buffer on the stack isn't sufficient?
> That's not easy when the exception is raised in case of a stack overflow.

In case of a stack overflow *anything* using the stack is doomed. But if we're talking about checking the stack it shouldn't be too hard to add some safety bytes to the check, should it?

But honestly, I don't understand the issue at all: How often would it happen that several threads try dumping their stack at the same time? In the real world, I mean?

I'd be for allocating the buffer statically and for MT safe code you still can add critical sections later. After all, dumping two stack traces at the same time wouldn't be very readable, neither. ;)


DSL-Preisknaller: DSL Komplettpakete von GMX schon für 
16,99 Euro mtl.!* Hier klicken: http://portal.gmx.net/de/go/dsl02

More information about the fpc-devel mailing list