SDBG crashing intermittently

Hi, anyone else getting this?

About 50% of the time, pressing F6 to start running my app under SDBG I get an 'access violation' and have to try again.

The other 50% I get a message like this:

Error

(i) System error: The parameter is incorrect

                                    [OK]

Clicking OK then runs the app correctly.

I've tried 'stepping' instead of 'running' but the same thing occurs.

Any ideas?

I'm using w7-64bit. SDBG v6.20.

K

This looks like it could be a problem about running SDBG under 64bit Windows 7. The best you can do is to make sure that all of your code is compiled using CHECKMATE.

It's quite a large app, with lots of DLLs, how much do I need to put under /CHECKMATE?

k

If you can, put everything under CHECKMATE whilst you isolate the current problem.

OK, I tried compiling everything with /checkmate but when I try to link my main DLL, I get this in SLINK:

Runtime error from program:c:\\win32app\\salford\\slink.exe
Access Violation
The instruction at address 00413499 attempted to write to location 0be28000

 004131ae writeExecutable(<ptr>char) [+02eb]

 0040767a parcelUpExe(void) [+097c]

 004081e9 processFileCommand(<ptr>char,int) [+023d]

 004088a9 processCommand(<ptr>char) [+0b20]

 0040a146 acceptCommands(void) [+00b0]

 0040c089 parseCommandLine(<ptr><ptr>char) [+02a3]

 0040cb94 main [+00c3]

 00426f8e SALFStart [+06ff]


eax=00003825   ebx=00c97dee   ecx=0be28000
edx=24eac000   esi=0be28000   edi=0b07f530
ebp=0370eca0   esp=0370ea54   IOPL=1
ds=002b   es=002b   fs=0053
gs=002b   cs=0023   ss=002b
flgs=00010202 [NC OP NZ SN DN NV]

 00413499  movh     [ecx],ax 
 0041349c  add      ecx,0x2 
 0041349f  mov      [ebp-0x34],ecx 

?

K

This looks like a bug in SLINK. If you can zip everything up and send it to Silverfrost, I will see if I can locate and fix the bug. I can see where the failure is occurring from your trace back but not why.

OK, it's on its way!

K

Paul, have you fixed this issue which seems i also got today under Win7_64. I started getting at the start of the debugging after first F6 the window

'System error: The parameter is incorrect'

which seems was just annoyance but then today the Variables window stopped to show any variables. The only difference was that today i used watch of variable and looked at the occurences of Write on variable.

Describing the problem a bit more -- when debugger starts i see the variables but after i switch the subroutine with Ctrl+F, its Variables window is empty. I could try to reinstall compiler but may be the problem is different

Later additions.... Switched OS to Windows XP 32 bit and there is the same story with Vars (no annoying System error window to appear though). That's totally strange, because compiler installations are different on different disks...(on XP this corruption might happened long ago - i did not use debugger there for a long time). Looks like a hardware problem?

I have everything to hand for Kenny's SLINK problem but I have not yet started to isolate the bug.

If you have a problem with SDBG then you should aim to isolate it in a small program and post it together with full details of your operating system.

Decently i even do not know how describe what is happening.... The behavior is reproduced on any program. For example this one

	program a
	aa = 1
	print*, aa
	call bsub
	end

	subroutine bsub
	bb=1
	print*,bb
	end

Next 3 pictures demonstrate what i do.

1. I open code in debugger (note its variables are listed), then
2. change the subroutine with Ctrl+F and
3. in opening windows do not see the variables. Fun is that this exactly happen in XP or Win7_64 (actually these pictures are from XP)

I don't think that you should expect to see any variables at this point. You have found the routine but you have not run the program to that point.

You will find the original break point in a window behind the window showing the 'Find'. Returning to the first code window shows the break point has not moved and the current variables are refreshed.

Wow Thanks for quick help, Paul. Seems i completely forgot how to use the debugger relying mostly on run-time errors. Or was confused with something....this popup or my error i still can not find or expecting vars to be there by default... some mental shift... 😃. I will remove these pics. By the way question to all - do 'real programmers use debuggers' ? 😃

Quoted from PaulLaidler I have everything to hand for Kenny's SLINK problem but I have not yet started to isolate the bug.

If you have a problem with SDBG then you should aim to isolate it in a small program and post it together with full details of your operating system.

OK, Paul, that new SLINK allows the '/CHECKMATE' compilation to complete successfully, thanks.

I'm now getting the following runtime error:

*** Error 14, Attempt to alter an actual argument that is a constant, an expression, an INTENT(IN) argument, or a DO variable

Which seems to be related to an ALLOCATED variable in a module in a DLL (in a large app!). The actual line of code itself looks completely benign so I've been trying to make a 'noddy' version that has the same issue, but haven't managed to reproduce it yet... (of course, it may be due to our 'recursive modules' problem...)

K