libgo patch committed: Don't allocate during backtrace
Ian Lance Taylor
Thu Jan 31 16:48:00 GMT 2013
The libbacktrace interfaces says that the strings passed to the callback
routine may disappear. As it happens, in the current implementation
they will not. The Go backtrace routine needs to hang on to the
strings, and I've discovered that it can't reliably allocate memory,
since it might be called in the middle of an existing memory
allocation. So at least for now just assume that the backtrace strings
will hang around. I'll fix this if I can figure out a way to allocate
memory there. Bootstrapped and ran Go testsuite on
x86_64-unknown-linux-gnu. Committed to mainline.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 835 bytes
More information about the Gcc-patches