News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

The 25 August 2012 build (8248) is out.

Started by killerbot, August 25, 2012, 08:06:20 PM

Previous topic - Next topic

const451

Hello,

I have the Aug 25 8248 build, when debugging Watch window does not show Local Variables and Function Parameters. Both are set in Debugger->Default by default and greyed out so it's not even possible to clear these settings.

How to enable those?

Thanks.

Edit: I am on Ubuntu.

oBFusCATed

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

const451

> The automatic inclusion of local variables and function arguments have not being reimplemented.

That's inconvenient. I hope it will be added back.

havefun

where is the vertical scrolled bar?I can't see it in your image!

ollydbg

Quote from: havefun on September 10, 2012, 10:35:49 AM
where is the vertical scrolled bar?I can't see it in your image!
Sorry, this is a mistake, should be "horizontal scroll bar".
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

nanyu

Why do not we use mingbuilds instead of TDM ?

mingwbuilds (NOT official ming) :  http://sourceforge.net/projects/mingwbuilds/reviews/

with mingwbuilds , we can try out all the C++11 features in this release of g++.

oBFusCATed

nanyu: Who stops you to install mingw instead of TDM?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

nenin

Quote from: nanyu on September 15, 2012, 11:36:15 AM
Why do not we use mingbuilds instead of TDM ?

mingwbuilds (NOT official ming) :  http://sourceforge.net/projects/mingwbuilds/reviews/

with mingwbuilds , we can try out all the C++11 features in this release of g++.
I use mingwbuilds  with c::b. And you can. Just do it.  :) But there are no any profit to build c::b with mingwbuilds now: mingwbuilds uses sjlj exceptions. 

nanyu

Quote from: nenin on September 15, 2012, 04:07:56 PM
Quote from: nanyu on September 15, 2012, 11:36:15 AM
Why do not we use mingbuilds instead of TDM ?

mingwbuilds (NOT official ming) :  http://sourceforge.net/projects/mingwbuilds/reviews/

with mingwbuilds , we can try out all the C++11 features in this release of g++.
I use mingwbuilds  with c::b. And you can. Just do it.  :) But there are no any profit to build c::b with mingwbuilds now: mingwbuilds uses sjlj exceptions. 

but c::b build with TDM uses sjlj exceptions also?

sophron

C::B becomes unresponsive, when watching big data structure on a debug session.
It has been an issue since the new debuggers branch merged into the C::B code base.

referring to
http://forums.next.codeblocks.org/index.php/topic,16868.0.html

Hadomunt

Quote from: nanyu on September 15, 2012, 11:36:15 AM
Why do not we use mingbuilds instead of TDM ?

mingwbuilds (NOT official ming) :  http://sourceforge.net/projects/mingwbuilds/reviews/

with mingwbuilds , we can try out all the C++11 features in this release of g++.

jaj C++11 (not sarcastic, sincere joy)

grooveordie

I am not sure if this is new or not, but I feel the need to share.

In debug watches window, a numeric array is shown like this:

array
   [0]   1 <repeats 23 times>
   [1]   5
   [2]   3 <repeats 4 times>


On strings this is useful, but on numeric arrays it might be a little bit confusing.

And in the debug watches window, if you want to rename a variable, you will see that the selection is not highlighted.

oBFusCATed

grooveordie:
What version of GDB is this?
I doubt it can be done anything about it, unfortunately.

About the second issue, yes this is a know issue and it is an issue of wxPropertyGrid, we are using for the watches.
When I was implementing the new watches, I've mentioned this issue to the creator of wxPropGrid and he said we will
see what can be done. But I think he is now missing. wxPropertyGrid is now merge inside wx2.9,
but I've not tried to use C::B compiled against wx2.9, so I don't know if this has been fixed there.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

grooveordie

GDB version 7.5. It is not a big problem, or not a problem at all but it would be useful to see [24] instead of [1] in the example i think.

Excuse me for re-mentioning a known issue, I didn't have time to check before.

Quote from: oBFusCATed on September 26, 2012, 09:28:57 PM
grooveordie:
What version of GDB is this?
I doubt it can be done anything about it, unfortunately.

About the second issue, yes this is a know issue and it is an issue of wxPropertyGrid, we are using for the watches.
When I was implementing the new watches, I've mentioned this issue to the creator of wxPropGrid and he said we will
see what can be done. But I think he is now missing. wxPropertyGrid is now merge inside wx2.9,
but I've not tried to use C::B compiled against wx2.9, so I don't know if this has been fixed there.

oBFusCATed

Quote from: grooveordie on September 27, 2012, 08:59:13 AM
GDB version 7.5. It is not a big problem, or not a problem at all but it would be useful to see [24] instead of [1] in the example i think.
This is doable probably, but I don't want to waste time with it as I'm re-writing the debugger plugin to use the more IDE friendly GDB/MI interface.
So I suppose this will be a non-issue there.

Quote from: grooveordie on September 27, 2012, 08:59:13 AM
Excuse me for re-mentioning a known issue, I didn't have time to check before.
No problem, if you have time/desire you can post it in the bug tracker at berlios.de, so it won't be forgotten as it is not written anywhere.

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]