Mail Archives: djgpp-workers/1998/03/30/10:55:15
> Is it a good idea to make our traceback symify itself (if the debug info
> is present)?
This was discussed for V1.11, and again for V2.0 in beta. The issues were
image bloat, complexity, and worse case behavior.
> If bloating the code of each program because of this is too much, maybe
> `abort' should do that? If that is still too much, how about a special
> debugging version of abort, for those who'd like that?
The early discussions included a special library to link against, or
potentially exec()'ing symify.
The worse case issues are when the stack is overrun, or a wild pointer
has scrogged code, or the exception table is corrupt. You may have a very
unstable enviroment to execute symify type code. The worry was this might
cause some hangs itself (a nesting type situation).
- Raw text -