I'm decompiling a few executables as part of a 'data recovery' exercise, and while JD is doing a pretty fantastic job, I've found that it's created in one instance a label that is out of scope of all of the "goto" commands that want to reach it. It seems that this is because the label is inside several 'while' loops, where it should actually be outside the topmost one.
Sadly I don't have the original source code that generated the executable, but I can send the executable if someone is brave enough to have a look at it and see why. In the meantime, I'll see if I can cause the problem with some smaller code.

Thanks for letting us know about this.

It'd be really nice if you could send over the executable and let us know where exactly that happens. Please, zip it and mail it over to tsviatko.yovtchev at . telerik.com

Greetings,
Tsviatko Yovtchev
the Telerik team

I've sent the email on, hopefully it's an easy fix.