I reported this problem as '"Asynchronous even occured" and "glibc detected" when opening form' back in May 29. I thot I had solved it, and when I discovered that it wasn't fixed afterall, the title got so long that it was changed (I don't know who changed it) to "ARSList Question NOT SOLVED AFTERALL".
The problem turned out to be a Red-Hat Linux issue. One of our Systems experts figured it out, and I'll simply pass on what he wrote to me: "There's a problem where double mallocs (double clearing of a memory allocation) causes a hard error in newer versions of RH Linux - the program crashes. The custom form in use here apparently does this somewhere in a function call. This is an issue we've dealt with (sort of) before and the systems guys just need to change a kernel paramater to cause a warning, versus error, to be generated when this occurs. This is the MALLOC parameter which, when set, causes a warning, versus hard error (crash) to be generated when a double clear occurs." Thanks to everyone who wrote in on this problem. Dwayne Martin Computing Support James Madison University _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
