SharpDevelop Community

Get your problems solved!
Welcome to SharpDevelop Community Sign in | Join | Help
in Search

Conditional Breakpoints

Last post 01-15-2007 12:42 AM by DavidSrbecky. 6 replies.
Page 1 of 1 (7 items)
Sort Posts: Previous Next
  • 12-01-2006 12:37 PM

    • Knower
    • Not Ranked
    • Joined on 12-01-2006
    • Posts 1

    Conditional Breakpoints

    Hi,

    first of all, "I love SharpDevelop".

    Even if it's not perfect yet, it has almost everything I need to program in C#. What's not implemented yet has to be done by BrainPower ;-)

    The thing I miss most in SD is support of "conditional breakpoints".

    I'm sure you've heared about this a lot of times and that you still have it on your feature list for future versions, but as I didn't find it here or by google search, I thought I'll mention it again.

     

    Filed under:
  • 12-03-2006 2:26 AM In reply to

    • DavidSrbecky
    • Top 10 Contributor
    • Joined on 08-22-2005
    • Usti nad Labem, Czech Republic
    • Posts 442
    • Team Members

    Re: Conditional Breakpoints

    Hi, thanks,

    Acutally, you are just only the second person to mention conditional breakpoints.  I personally never used them.  Could you describe what specific features you are looking for.  What do you need the most?

    David
     

  • 01-14-2007 10:50 AM In reply to

    Re: Conditional Breakpoints

    Hi David,

    Although most things in SD work really well, the debugging function is very basic, and I would like:

    1. Conditional breakpoints (I don't know about the other guy, but in my case): e.g. instead of always stopping at a certain point, only if a certain condition is fulfilled. In my case, this often occurs in loops, such as i>130; --> stop or if myBoolean == true;
      It could be implemented by right-clicking on a BP.
    2. The speed should really be improved: at the moment, it is very slow (esp. I think when there are many local variables), and I've noticed that it even becomes worse after running the same function a couple of time. In the current release SD2.1 build 2201, I often need to close the application and restart it when speeds have dropped to unbearable (e.g. pressing F10 to step a function takes more than 5 seconds on a 1y old PC)
    3. Stepping through a function with F10 shouldn't stop at 'empty' lines, e.g. lines only containing a {
    4. Watches, not only for objects, but also for data, e.g. myObject.myField
    5. Display of values should not only be in decimal value, but also in hex or binary (or octal).
    6. It would be nice if, when debugging an image, I could point to an image in the Debugger and it would show how it looks like in the tooltip.
    7. Implement a function "Run to cursor", e.g. select a line, and tell the debugger to run until that point (like a temporary BP, but a bit faster)
    8. Why is F5 Build and run, whereas F6 is continue to run (why not use F5 for both?)
    9. Bug: When the cursor is on a certain line, you cannot use the mouse anymore to toggle the BP (you have to press F7 to do that)

    That's it for now!

    Thanks,
    Erik
     

  • 01-14-2007 11:46 AM In reply to

    Re: Conditional Breakpoints

    Hi all,

    I confirm each point of Erik's post. The debugging feature of #D could be very faster.

    Normally, I don't use conditional breakpoints (like David). But in loops (like Erik's #1), this would be a very practicable improvement.

    Please, improve debugging in this way! Juergen 

    Software fuer Verlage (Publishers)
    #D + NET 2.0 + Firebird 2.0
    (formerly Delphi 5 + 2005 Pro)
  • 01-14-2007 4:12 PM In reply to

    • DavidSrbecky
    • Top 10 Contributor
    • Joined on 08-22-2005
    • Usti nad Labem, Czech Republic
    • Posts 442
    • Team Members

    Re: Conditional Breakpoints

    1, 4, 6, 7 - I moved these up at IntegratedDebuggerPlans. I definately plan to implement theses features, I just have no idea when I will have enough time to do so.

    2 - I am working on this

    3 - This is not my call. I work with what the compiler gives me.

    5 - Hex is already supported in tooltips. Is binary and octal sensible?

    8 - "because the current SharpDevelop core does not allow using a single shortcut for multiple commands depending on the conditions used for those commands" -- Daniel Grunwald

    9 - I agree that migh be annoying
  • 01-14-2007 11:13 PM In reply to

    Re: Conditional Breakpoints

    Thanks David, that's great to hear! Unfortunately I am currently moving from Sydney, AU, back to The Netherlands, so I am not able to help you - maybe somebody else can...

    About tooltips: I didn't know that you can turn on hex display (how can I turn that one?), which is clearly the most important one - sometimes, binary is useful too, e.g. when checking which flags (bits) are set.

    Second, it would be good that when pointing to a field, the value of the field would be shown in the tooltip, e.g. e.Message would give the message text, instead of finding the text by browsing through the whole object's tree. In addition, when browsing through an object, maybe you can maintain that state as well, so that the next time you point to e, it will open up as the last time, and you can immediately see the field you've selected previously.

    Finally, about Image tooltips: for Visual Studio, here's an interesting example on The Code Project:

    http://www.codeproject.com/csharp/ImageVisualizer.asp

    Cheers,
    Erik 

     

     
     

  • 01-15-2007 12:42 AM In reply to

    • DavidSrbecky
    • Top 10 Contributor
    • Joined on 08-22-2005
    • Usti nad Labem, Czech Republic
    • Posts 442
    • Team Members

    Re: Conditional Breakpoints

    You can turn on the hex display in the context menu (right-click on the value in the tooltip)

    "e.Message" should in theory work 

Page 1 of 1 (7 items)
Powered by Community Server (Commercial Edition), by Telligent Systems
Don't contact us via this (fleischfalle@alphasierrapapa.com) email address.