On Mon, 27 Dec 2004, Tim Jenness wrote:
> * idi
> Not sure why this fails on debian with a SEGV. A code dump would
> be extremely handy. I've run messgen through valgrind and don't find
> any errors from there (is it failing with the IDI_ERR build? if so
> does
> messgen -F idi_err.msg
> trigger the segv?
Yes, the problem is a buffer overrun (line 326 of messgen.c). Surprised
valgrind didn't see this one.
The problem is that the char[] message_ident permits only 10 characters,
whereas IDI now has identifiers a few characters greater than that (the
one that does the actual damage is VD_SAVENOTALL). Identifiers can be up
to 15 characters (ems1Fcerr.c), so I've attempted to make the necessary
changes. Haven't checked this under Debian...
Peter.
|