Re: wxEuphoria (again)
- Posted by ghaberek (admin) Feb 16, 2010
- 1881 views
jimcbrown said...
Jerry_Story said...
Ah! Maybe that is why dmak produced a segmentation error after loading data. I typed those 2 lines correctly and the error disappeared.
This sound like a genuine bug in wxEuphoria or dmak...
The wxEuphoria library has little-to-no internal error checking. Most errors end in a segfault. On Windows, this typically results in a "the stack data has been corrupted!" message. I'm sure later versions of the library will have more appropriate error checking.
-Greg