While I've run into the "Exception" popup many times as I've developed GXs written in C++, I've always been able to find the problem without having to decode the contents of abort.log file that this popup generates. However, I've run through all my other alternatives and can't think of anything else to do but dig into this report to see if it gives me a clue on what I'm doing wrong. Does anyone have any information on decoding this report? Also, does this popup appear as soon as the infraction is detected or might the infraction occur in a separate thread and get reported at a later time? Regards, David L. Humphrey Manager, Software Development Bell Geospace, Inc _______________________________________________________ More mailing list info http://www.geosoft.com/support/listserv/index.html List Archive http://www.mail-archive.com/gxnet@lists.geosoft.com
