VC++ 6.0 string bug ? (take a look plz)
-
Your code works fine for me as well in both Debug and Release builds on WinXP Pro. That is I "anystringabcde" Have you tried rebooting Windows? If all else fails... Neville Franks, Author of ED for Windows. www.getsoft.com
This is a very strange problem... rebooted, underclocked the processor, I have no idea... it still gives me different results: In Debug "anystringabcde" In Release "anystringBUG!" When Optimizations is MazimizeSpeed(default setting) Thanks for your time :(
-
This is a very strange problem... rebooted, underclocked the processor, I have no idea... it still gives me different results: In Debug "anystringabcde" In Release "anystringBUG!" When Optimizations is MazimizeSpeed(default setting) Thanks for your time :(
Have you tried stepping through it in the debugger and seeing where 'result' screws up. You can still debug release builds by including debug info. I think there is an article by Mr. Newcomer here on CP about this. Neville Franks, Author of ED for Windows. www.getsoft.com
-
Have you tried stepping through it in the debugger and seeing where 'result' screws up. You can still debug release builds by including debug info. I think there is an article by Mr. Newcomer here on CP about this. Neville Franks, Author of ED for Windows. www.getsoft.com
I have found the article, thanks! Very interesting http://www.codeproject.com/debug/survivereleasever.asp) But life is hard: I have turned on debugging information for Release and the compiler gives me this error asa I press F5: "Command line error D2016 : '/ZI' and '/O2' command-line options are incompatible" /O2 is the parameter for the Optimization->MazimixeSpeed, and if I turn it OFF the bug doesn't appear, so debugging is useless in this case! Nice... Maybe I have to reinstall, I don't know
-
I have found the article, thanks! Very interesting http://www.codeproject.com/debug/survivereleasever.asp) But life is hard: I have turned on debugging information for Release and the compiler gives me this error asa I press F5: "Command line error D2016 : '/ZI' and '/O2' command-line options are incompatible" /O2 is the parameter for the Optimization->MazimixeSpeed, and if I turn it OFF the bug doesn't appear, so debugging is useless in this case! Nice... Maybe I have to reinstall, I don't know
You can still debug but you'll need to be able to work through the Assembler code. If you started with Assembler like I did this isn't too difficult. Another option is to use: OutputDebugString() Neville Franks, Author of ED for Windows. www.getsoft.com
-
You can still debug but you'll need to be able to work through the Assembler code. If you started with Assembler like I did this isn't too difficult. Another option is to use: OutputDebugString() Neville Franks, Author of ED for Windows. www.getsoft.com
Debugging assembler is a dying skill. :( Thank god I learned it years and years ago. I use that skill all the time. Tim Smith I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?
-
Debugging assembler is a dying skill. :( Thank god I learned it years and years ago. I use that skill all the time. Tim Smith I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?
Tim Smith wrote: Debugging assembler is a dying skill. Thank god I learned it years and years ago. I use that skill all the time. Yes I couldn't agree more. My guess is that these days most programmers wouldn't have a clue about Assembler. I started programming in Signetics 2650 Assembler with 8K RAM, and spent a number of years writing Z80/8080 Assembler. In fact the very first versions of my programmers editor (ED) were writtem in 2650 Assembler. It sure has come an awefully long way to what you see today. Thank god for C/C++, but having said that I still dip in to the Assembler listings from time to time while debugging. I would also take a punt and say many developers today don't use a Debugger enough. Neville Franks, Author of ED for Windows. www.getsoft.com
-
Tim Smith wrote: Debugging assembler is a dying skill. Thank god I learned it years and years ago. I use that skill all the time. Yes I couldn't agree more. My guess is that these days most programmers wouldn't have a clue about Assembler. I started programming in Signetics 2650 Assembler with 8K RAM, and spent a number of years writing Z80/8080 Assembler. In fact the very first versions of my programmers editor (ED) were writtem in 2650 Assembler. It sure has come an awefully long way to what you see today. Thank god for C/C++, but having said that I still dip in to the Assembler listings from time to time while debugging. I would also take a punt and say many developers today don't use a Debugger enough. Neville Franks, Author of ED for Windows. www.getsoft.com
I learned on the 8080/85, Z80, and 6809 processors. Ah, the good old days. My first C compiler was ECO-C. This was back in the days when a C compiler generated ASM code which you then sent into the assembler. Tim Smith I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?
-
You can still debug but you'll need to be able to work through the Assembler code. If you started with Assembler like I did this isn't too difficult. Another option is to use: OutputDebugString() Neville Franks, Author of ED for Windows. www.getsoft.com
I have a little experience with ASM, learnt at Uni and played at home, I'll give a look at it but maybe another problem has come out. I have installed WinXP few weeks ago and I notice that no symbols are found during debugging. Maybe I have to download this 150MB package from MS site (windowsxp.x86.fre.rtm.symbols.exe) Another strange thing appened: if I put AfxMessageBox(s1) before strcpy(), the bug vanishes: void Buggy( char* result ) { char s1[6]; char s2[5]; strcpy(s1,"abcde"); strcpy(s2,"BUG!"); AfxMessageBox(s1); // DOESNT WORK strcpy(result,"anystring"); strcat(result,s1); } It displays "abcde" and 'result' is filled with "anystringabcde". If I comment out AfxMessageBox(s1) 'result' is filled with "anystringBUG!". I have made several programs, some little, others bigger, but I had never seen these strange beahviours, especially because on other PCs compiles fine. I must admit that I'm not expert in debugging, I prefer to proceed slowly, and run the program just after having added/removed some lines of code. Lately I have installed and removed MySQL, MSDE, various ServicePacks, maybe something has been wrong and I didn't notice.
-
I have a little experience with ASM, learnt at Uni and played at home, I'll give a look at it but maybe another problem has come out. I have installed WinXP few weeks ago and I notice that no symbols are found during debugging. Maybe I have to download this 150MB package from MS site (windowsxp.x86.fre.rtm.symbols.exe) Another strange thing appened: if I put AfxMessageBox(s1) before strcpy(), the bug vanishes: void Buggy( char* result ) { char s1[6]; char s2[5]; strcpy(s1,"abcde"); strcpy(s2,"BUG!"); AfxMessageBox(s1); // DOESNT WORK strcpy(result,"anystring"); strcat(result,s1); } It displays "abcde" and 'result' is filled with "anystringabcde". If I comment out AfxMessageBox(s1) 'result' is filled with "anystringBUG!". I have made several programs, some little, others bigger, but I had never seen these strange beahviours, especially because on other PCs compiles fine. I must admit that I'm not expert in debugging, I prefer to proceed slowly, and run the program just after having added/removed some lines of code. Lately I have installed and removed MySQL, MSDE, various ServicePacks, maybe something has been wrong and I didn't notice.
Frankesk wrote: Lately I have installed and removed MySQL, MSDE, various ServicePacks, maybe something has been wrong and I didn't notice. Maybe one of the MFC DLL's has gone back to an old version. About now I'd suggest re-installing VC++. Neville Franks, Author of ED for Windows. www.getsoft.com
-
Frankesk wrote: Lately I have installed and removed MySQL, MSDE, various ServicePacks, maybe something has been wrong and I didn't notice. Maybe one of the MFC DLL's has gone back to an old version. About now I'd suggest re-installing VC++. Neville Franks, Author of ED for Windows. www.getsoft.com