-----------------------------------

StealthArcher

Mon Feb 25, 2008 11:59 am


Strange Behaviour

-----------------------------------

I'm making a program for class at school, and attempting to use the button class of cervantes that I tweaked a bit.

However, it seems that over the last week (seriously) it has decided to stop working altogether, it constantly throws up a "breakpoint reached" error when Im executing, I can ignore, but then the text is gone.

Any ideas what is happening?


-----------------------------------

OneOffDriveByPoster

Mon Feb 25, 2008 2:33 pm


Re: Strange Behaviour

-----------------------------------

However, it seems that over the last week (seriously) it has decided to stop working altogether, it constantly throws up a "breakpoint reached" error when Im executing, I can ignore, but then the text is gone.Sounds like you accidentally set a breakpoint in your program.  See if there is a way to unset the breakpoint.


-----------------------------------

ericfourfour

Mon Feb 25, 2008 6:00 pm


RE:Strange Behaviour

-----------------------------------

1. Run -> Show Debugger Menu
2. Debugger -> Clear Breakpoints


-----------------------------------

StealthArcher

Mon Feb 25, 2008 6:16 pm


RE:Strange Behaviour

-----------------------------------

Ooooookayyy.  Seeing as I couldn't get on for a while( had the internet shut off for a fax incoming, need another phone line, or filter or something, I'd do it myself but it's not my house :P) , when I got back on I went straight to get a new turing 4.1.1 dload thinking it might have been a faulty download lat time.  I got a different error this time:
The value of ESP was not properly saved across a function. This is usually a result of calling a function declared with one calling convention with a pointerdeclared with a different calling convention.

Is this a segfault?

Ooookay, with the old turing dload, on my memstick I get this error: DAMAGE: after normal block ((#4531 at 0x011F0040


-----------------------------------

OneOffDriveByPoster

Mon Feb 25, 2008 6:41 pm


Re: RE:Strange Behaviour

-----------------------------------

The value of ESP was not properly saved across a function. This is usually a result of calling a function declared with one calling convention with a pointerdeclared with a different calling convention.My random guess is that you have mismatched DLLs...


-----------------------------------

StealthArcher

Mon Feb 25, 2008 7:09 pm


RE:Strange Behaviour

-----------------------------------

Okay, I feel like such an idiot now.

I was trying to make the INIT function call Font.Set while in text mode.   :oops:  sorry everyone.