🚀 go-pugleaf

"Jeroen Stiekema" <developer@winkhem.com> wrote in message 
news:41a44a9f@newsgroups.borland.com...
> The problem is that I have to step into tenthousands of assembly lines
> before I come back to my own code. Normally I can add a new breakpoint 
> to
> the next line and press the green playbutton to skip the assembly, but 
> in
> this case it is unknown in which line I come back. That's why I need to 
> use
> the debugger, because I want to know which code is going to run after 
> the
> assembly.
> I code a lot in Java-IDE's where you have the option to skip 
> Java-framework
> code while debugging. I wonder if the C#Builder has some sort of option 
> to
> let the debugger skip the assembly code.

I don't quite understand your problem. As per my previous post you can 
just press Run and close the disassembly window. If you have set 
breakpoints in your code it will stop where directed.

The debugger isn't fully stable in C#B. I guess D2005 is better.

If the C#B debugger is unworkable in your case you can use the debugger 
that is delivered with .Net. In my machine it is at "C:\Program 
Files\Microsoft.NET\SDK\v1.1\GuiDebug\DbgCLR.exe".

Start your program outside the IDE, then attach the Microsoft debugger. 
All the facilities (breakpoints, view variables etc) work ok.

Barry Mossman