U++ framework: U++ TheIDE: Other Features Wishlist and/or Bugs

Home » U++ TheIDE » U++ TheIDE: Other Features Wishlist and/or Bugs » Debugger feature request

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Debugger feature request [message #35462]

Mon, 20 February 2012 10:29

unodgs
Messages: 1367
Registered: November 2005
Location: Poland

Ultimate Contributor

Would be possible to add the option "don't step into Core"? I mean very often during debugging I'm taken to the body of for example Vector::GetCount() or Rect class' constructor. That takes time and from my application point of view is only time wasting.
In IntelliJ idea if someone really wants to debug standard library he presses another debugger shortcut (it could be shift-f11 for instance in theide)

[Updated on: Mon, 20 February 2012 10:31]

Report message to a moderator

Re: Debugger feature request [message #35463 is a reply to message #35462]

Mon, 20 February 2012 12:04

cbpporter
Messages: 1428
Registered: September 2007

Ultimate Contributor

unodgs wrote on Mon, 20 February 2012 11:29

I second that! In fact I suggested that a long time ago. I think my simple solution was to automatically step over things in the Upp namespace, but I'm not sure this can be done easily.

An another think I would greatly appreciate: currently you can't have two variables with the same name in different block. The debugger gets confused by this. This is really annoying because every for loop variable needs a different name.

And debugging inspecting global variables and static class members would be great too.

I sincerely love U++ and use it to great results on a day by day basis, but TheIDE is clearly the weakest link. Never mind that it somehow gets confused and start misinterpreting key presses at least once every two days.

Report message to a moderator

Re: Debugger feature request [message #35464 is a reply to message #35463]

Mon, 20 February 2012 12:24

unodgs
Messages: 1367
Registered: November 2005
Location: Poland

Ultimate Contributor

cbpporter wrote on Mon, 20 February 2012 06:04

An another think I would greatly appreciate: currently you can't have two variables with the same name in different block. The debugger gets confused by this. This is really annoying because every for loop variable needs a different name.

And debugging inspecting global variables and static class members would be great too.

I'd love to see it fixed as well. Another missing thing is showing container elements. Currently only data from first element is visible.

Report message to a moderator

Re: Debugger feature request [message #35524 is a reply to message #35464]

Sat, 25 February 2012 10:28

281264
Messages: 272
Registered: June 2010
Location: Spain

Experienced Member

I agree with you guys. Certainly, any improvement in the debugger would be very welcome. For example, the debugger is not able to inspect the STL containers (vector, etc,..); although in U++ we have our NTL, sometimes it is convenient to use the STL.

Best regards,

Javier

Report message to a moderator

Re: Debugger feature request [message #35526 is a reply to message #35524]

Sat, 25 February 2012 14:10

mdelfede
Messages: 1310
Registered: September 2007

Ultimate Contributor

For Linux part, using the new MI2 interface, it's quite easy to add STL support... The python code it's even ready to download somewhere and it's enough to add it to PrettyPrinters.py code.

About the windows part, my knowledges are too limited....

Max

Report message to a moderator

Re: Debugger feature request [message #35550 is a reply to message #35526]

Wed, 29 February 2012 08:03

mirek
Messages: 14291
Registered: November 2005

Ultimate Member

I think there should and will be Windows refactoring, adding win64 support and matching MI2 capabilities.

But I guess it is gona happen in next cycle (or somebody else has to do it Wink