Originally posted by 123ANDREW456

---

Ok I did that but now it says Run-Time error 6 Over flow! How do I fix this?

---

Originally posted by sloat

---

With Visual Studio, I'm pretty sure you have to run the app through the IDE. I'm not 100% sure though and I'm not sure if that applies to Bloodshed. It could also be that your breakpoint is just never reached.

---

Launching your program into the debugger is easy. Just go to the Debug menu and click on Debug (shortcut : F8).
If you do not have debugging information set in your project, Dev-C++ will ask you if you want to rebuild your program with these information enabled. You can manually select that option in Compiler Option in the Linker section. After your project has been rebuild, you can launch Debug again.


The debugger has now loaded your program and runs it. but until that you can learn to control several aspects of the debugger :

- Setting Breakpoints in your codeID_BREAKPOINT

- Stepping in your codeID_STEPDEBUG

- Displaying variables value and classes/structures membersID_DISPLAYDEBUG

- BacktracingID_BACKTRACE

- Using the CPU WindowID_CPUWINDOW

The output Dev-C++ receives from GDB is displayed in the Debug Output sheet at the bottom of Dev-C++.

This output is probably only interesting if you are familiar with GDB. You can also send commands directly to it (if you do not know GDB, you can type the help command for to have a list) by using the edit box just above the output (see screenshot below).

Originally posted by Kawa-oneechan

---

I myself required some nice debugging myself. YDimGame kept resetting to zero! So I peppered my code with printf("DEBUG: YDimGame is now %d\n", ydimgame); lines.

Eventually, I found that my game's config routines were loading the player's pant color into ydimgame


So yeah, PrintF for the win.

In VB, I just click auto-comment and remove apostrophes until it breaks, basically.

---

Originally posted by Smallhacker

---

how do u maek smb 4 teh nes uze 3D grafix buy canging an max off 10 bytes?

...What? It IS a question about Rom Hacking.

---

Originally posted by Disch

---

the WM_KEYDOWN repeat rate is one of the user preferences set in Windows (the speed can be changed in one of the control panels), so no, you're program can't (or at least shouldn't) try to change the speed at which WM_KEYDOWN messages are sent.

The obvious solution here sounds to me like you should just not process WM_KEYDOWN messages if your program is too far behind. This could be done by doing some checks in your message pump:

---


MSG msg;
int ok_to_sleep;
while( program_open )
{
ok_to_sleep = 1;
while( PeekMessage( your_wnd, &msg, 0, 0, PM_REMOVE) )
{
TranslateMessage(&msg);
DispatchMessage(&msg);
ok_to_sleep = 0;
}

program_busy = 0; // queue is clear, program is no longer busy

if(ok_to_sleep)
Sleep(1);
}


---

Then in your ChangePipeSets function or whatever.. just do a check to see if the program is busy before continuing:

---


void ChangePipeSets()
{
if(program_busy) return; //abort, program is too busy

program_busy = 1; //this will make the program busy

// do the rest of the work here
}


---

---

Originally posted by Snika

---

Oh no! Save the Mardi Gras beads!
Stalk up on Cajun food and other sterotypes!
Evacuate to France!

---

Originally posted by Snika

---

It would just go underwater?
Would any other states be effected?

---

Originally posted by Snika

---

That must suck! Isn't there anything we can do?

---

Originally posted by Snika

---

I'll alert the president!

---

Originally posted by Snika

---

Oh, thats a good thing that the president declared a state of emergency.
It cracks me up that he was vacationing when he got the memo.

---

Originally posted by Bella

---

New Orleans sinking? doesn't seem very likely

I didn't even know there was a hurricane heading there until this morning since I haven't really checked the news when I log on.

---

Originally posted by HyperHacker

---

Presumably a really simple question, but I can't seem to find an answer. How can I delete a byte from the middle of a file (in Binary mode, in C)?

---

malloc.h>
#include <io.h>
#include <fcntl.h>
#include <sys\stat.h>

int deletebyte(const char *filename, int address) {
int size, handle, *data;
FILE *nfo;

handle = open(filename, O_RDONLY); /* getting file size */
size = filelength(handle);
close(handle);

data = malloc(sizeof(int) * size); /* creating data space in memory to store file*/

nfo = fopen(filename, "rb"); /* loading the file */
for(int i = 0; i < size; i++)
data[i] = fgetc(nfo);
fclose(nfo);

for(int i = address + 1; i < size; i++) /* starting at the byte following the specified address */
data[i - 1] = data[i]; /* shifting each byte left */

size--; /* decrementing the size */

nfo = fopen(filename, "wb"); /* reopening the file to write to it */
for(int i = 0; i < size; i++) /* writing to it */
fputc(data[i], nfo);
fclose(nfo);

/* now that we did it, it's time to return our value and free our dynamically allocated array */

free(data);

return size; /* returning our new file size */
}

/* if you want to use this function call it: the first parameter is the file name and the second parameter is the address that you want to delete; the function returns an int, the new filesize of the file. */

---

(edited by beneficii on 08-28-05 06:18 AM)
(edited by beneficii on 08-28-05 06:19 AM)
(edited by beneficii on 08-28-05 06:20 AM)
(edited by beneficii on 08-28-05 06:21 AM)
(edited by beneficii on 08-28-05 06:44 AM)