User forums > Using Code::Blocks
Problem with Debugger when upgrading MinGW
recobb:
--- Quote from: ollydbg on February 14, 2011, 02:18:41 am ---
--- Quote from: recobb on February 13, 2011, 04:41:50 pm ---If I open the data file located in the project folder, single stepping works. Open in a different folder, and it does not.
--- End quote ---
This was too strange, I will test it tonight.
BTW: I guess: does your anti-virus program cause this problem??? :D
--- End quote ---
I don't think so - I don't have the problem using the 6.8 version. I'm using Commodo, for whatever that is worth.
I've been wondering if somehow, when using the file open dialog, some path is set to the new location and it loses some connection to the source files in the project folder. But that doesn't really make sense either, as I can set breakpoints in the source file and those still work. I could effectively single step by setting a breakpoint at every line, then resuming at each breakpoint - but that's not a happy way of doing things :(
ollydbg:
so, the problem(gdb complain memory access error) only happens when you open a file in a different folder(not the project folder)?
recobb:
--- Quote from: ollydbg on February 14, 2011, 02:28:05 am ---so, the problem(gdb complain memory access error) only happens when you open a file in a different folder(not the project folder)?
--- End quote ---
That's right - if I open the data file while it's in the project folder I don't have a problem. It's only when I have to navigate to a different folder (using the file dialog) that the problem appears.
recobb:
--- Quote from: recobb on February 14, 2011, 02:33:12 am ---
--- Quote from: ollydbg on February 14, 2011, 02:28:05 am ---so, the problem(gdb complain memory access error) only happens when you open a file in a different folder(not the project folder)?
--- End quote ---
That's right - if I open the data file while it's in the project folder I don't have a problem. It's only when I have to navigate to a different folder (using the file dialog) that the problem appears.
--- End quote ---
Well, it gets stranger and stranger. This morning I created a new project (with a different project name) in the same folder as the files for the test case. I went through the wizard, created a blank wxwidgets project, then added the .cpp files from the other project once it was created. The problem with single-stepping was not present. OK, so it's something to do with the project settings I thought to myself. So I went and rebuilt the project as included in the zip test case. The problem had disappeared there too! OK, so maybe there are some files that are being updated from one project that affect the other. I did a 'clean' and verified that all object files and executables were removed (or I deleted them myself). I also checked the dates of all the files in the main project folder. The only files newer than the zip file I posted were for the newly created project (a .cbp and .depend), and a .layout file for the original project. I opened the .layout file in an editor and could not see anything in there that would affect anything (it was only a couple of lines long). I rebuilt again and tried the debugger - it's now working (this is the tdw version) as it should.
OK, so all I need to do is create a new project for my original (full) project, which I did. The Single Step Problem is Still There... :?
The Full Moon is only 4 days away, maybe that's it.
stahta01:
Note: The below assumes the OP is a Vista or Windows 7 user.
@recobb: You do realize that Vista and Windows 7 have different permissions per folder.
If either one of the below fixes the problem.
1. Run Code::Blocks as Admin does the problem go away.
2. Turn off UAC and if problem goes away it is a Windows Security issue.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version