🚀 go-pugleaf

On Tue, 23 Nov 2004 09:48:05 +0100, Jeroen Stiekema wrote:

> Hi,
> 
> Is there an option to disable debugging in assembly code? I'm using a
> activeX component, and it is really nice I have to press f7 for 10 hours to
> step into the assembly code, but it is really useless to see the assembly in
> debug mode. Is there an option to skip the assembly? I only want to show the
> c# code. Can anyone help me?

You should be able to apply the DebuggerHidden or DebuggerStepThrough
attribute to methods to prevent debugging. I don't know of anything
that works for a whole assmebly although you could try using the
Debuggable attribute.

-- 
Marc Rohloff [TeamB]
marc rohloff at myrealbox dot com

"Marc Rohloff [TeamB]" <"on request"> wrote in message 
news:1asoh3x6dqcev$.dlg@marcrohloff.40tude.net...
> On Tue, 23 Nov 2004 09:48:05 +0100, Jeroen Stiekema wrote:
>
>> Hi,
>>
>> Is there an option to disable debugging in assembly code? I'm using a
>> activeX component, and it is really nice I have to press f7 for 10 
>> hours to
>> step into the assembly code, but it is really useless to see the 
>> assembly in
>> debug mode. Is there an option to skip the assembly? I only want to 
>> show the
>> c# code. Can anyone help me?
>
> You should be able to apply the DebuggerHidden or DebuggerStepThrough
> attribute to methods to prevent debugging. I don't know of anything
> that works for a whole assmebly although you could try using the
> Debuggable attribute.

I think that he means the annoying Disassembly window that comes up 
whether you want it or not. I think that it is a bug in C#B.

I just close the window whenever C#B opens it.

I guess that the real fix is to get D2005 <g>   ... hopefully

Barry Mossman 

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.

"Marc Rohloff [TeamB]" <"on request"> schreef in bericht
news:1asoh3x6dqcev$.dlg@marcrohloff.40tude.net...
> On Tue, 23 Nov 2004 09:48:05 +0100, Jeroen Stiekema wrote:
>
> > Hi,
> >
> > Is there an option to disable debugging in assembly code? I'm using a
> > activeX component, and it is really nice I have to press f7 for 10 hours
to
> > step into the assembly code, but it is really useless to see the
assembly in
> > debug mode. Is there an option to skip the assembly? I only want to show
the
> > c# code. Can anyone help me?
>
> You should be able to apply the DebuggerHidden or DebuggerStepThrough
> attribute to methods to prevent debugging. I don't know of anything
> that works for a whole assmebly although you could try using the
> Debuggable attribute.
>
> -- 
> Marc Rohloff [TeamB]
> marc rohloff at myrealbox dot com

"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 

"Jeroen Stiekema" <developer@winkhem.com> wrote:
>The problem is that I have to step into tenthousands of 
> assembly lines before I come back to my own code. 

I don't have c# builder installed so this is only a guess but you could try opening the regedit and setting the value of:

HKEY_CURRENT_USER\Software\Borland\BDS\1.0\Known IDE Packages\$(BDS)\Bin\asmview71.bpl

To an empty string to disable it.

--
Marc Rohloff [TeamB]
marc rohloff at myrealbox dot com