This project is read-only.


Error in debugger


After setting conditional breakpoint(memory change) the following error occurrs(see attachment JIT_error.png)

Steps to simulate:
1.) open Debugger adlers
2.) enter following breakpoint: br (26072) != #5d


I am pretty sure it worked in the past. But, something in code caused this breakpoint type working no more.

file attachments

Closed Jan 28, 2015 at 10:26 AM by Adlers
Funny, error found in my own code..:-)

Thank for your help.


zxmak wrote Jan 23, 2015 at 10:00 PM

it seems that there is some mistake in the emitted code, may be there is reached limit for local variables or something like that.
I will look it

zxmak wrote Jan 23, 2015 at 11:27 PM

I checked your issue, it appears because you have the following code in the DebuggerManage.EmitCondition:
            case "!=":
                //ToDo: i_ILGenerator.Emit(OpCodes.Ceq);
I will add implementation for this.

By the way, please NEVER delete files, use move operation instead of delete and create new.
Because you deleted all history for this file... I will try to restore it, but please do not delete files in future.
You can simple move file in solution explorer, if you are moving file inside project. Or you can open Team Explorer and use Move command to move file from one location to another.

zxmak wrote Jan 23, 2015 at 11:54 PM

Adlers, please do not use catch block without logging.
Exception is exceptional state and should be always logged.
If you don't want to see exceptions in the log, add checks to avoid exceptions.
If you write catch {}, you will never see exceptions which signals about serious troubles in the code.

When the code catch exceptions and cannot handle it properly, such code is marked as problematic in the code analysis tools and error message will appears on attempt to compile such code. This is very bad. Please do not use it.

zxmak wrote Jan 24, 2015 at 12:12 AM

and please do not use throw exception of type Exception. Especially from catch block.
You're hiding typed exception which can be handled properly with general exception which cannot be handled.

zxmak wrote Jan 24, 2015 at 12:22 AM

if you write catch for all exceptions then you doing something wrong

zxmak wrote Jan 24, 2015 at 1:45 AM

I fixed your issues, try to install resharper it will help you to find errors such as catch exception without logging and many other ;)

zxmak wrote Jan 24, 2015 at 1:50 AM

Also you can read about CA1031:
It's rule violation about catch exception without logging ;)
And it's why I fixed it

zxmak wrote Jan 24, 2015 at 1:58 AM

If you want to catch some type of exception and handle it, just catch specific exception.
But if you catch general exception of type Exception, it should be always logged.

wrote Jan 28, 2015 at 10:26 AM