Recent Posts

Pages: 1 2 3 4 5 [6] 7 8 9 10
51
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by oBFusCATed on June 23, 2017, 12:04:21 am »
M$'s comm. ed.
Are you talking about visual studio?

Do you want my opinion about a development chain where nothing fits together, and debugging vector[1] is impossible?
This won't change anything. Patches improve the situation. Ranting is just ranting.

OK, if the python scripts have to match the c++ standard library ... I moved the original scripts (from mingw 4.9.2) back.
Effect: same effect.
Yes, they need to match, because the standard library changes its internals and the python script need to know the internals of the library.

Does gdb has to match too?
Only to the point that the Python APIs used in the scripts are compatible. But I think the gdb's python apis are relatively stable.

@bluehazzard: Does this example work for you?
52
Help / Re: Upgrading CB 13.12 to 16.01 failed saving config files.
« Last post by oBFusCATed on June 22, 2017, 11:58:12 pm »
If you can reproduce it multiple times then it is probably a bug.
We need exact steps to reproduce the problem.
We need the state of your ~/.codeblocks folder before upgrading and the state of ~/.config/codeblocks after the upgrade.

note: When running as root ~ is /root not /home/yourusername or something similar.
53
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by nji on June 22, 2017, 11:34:08 pm »
No, I'm not sure at all if anything matches together. I just downloaded the "updates" as pointed to in http://forums.codeblocks.org/index.php/topic,21998.msg149716.html#msg149716.
Sigh ... do you need any more explanation why M$'s comm. ed. is so popular?
Do you want my opinion about a development chain where nothing fits together, and debugging vector[1] is impossible?
...
OK, if the python scripts have to match the c++ standard library ... I moved the original scripts (from mingw 4.9.2) back.
Effect: same effect.
Does gdb has to match too?
This becomes ridiculous and frustrating.
54
Help / Upgrading CB 13.12 to 16.01 failed saving config files.
« Last post by dmarques on June 22, 2017, 09:58:59 pm »
After upgrading from CB 13.12 to 16.01, on Ubuntu 14.04, I have found a problem.

During the first CB 16 run, it says the config files (at "~/.codeblocks" on CB 13.12) must be moved to "~/.local/share/codeblock".

However, CB 16.01 never gets to save config files to that new dir.

At first, CB 16 wasn't saving anything so, checking the messages on a terminal, (while quitting) it said it could not save the config file (default.conf I guess).

The ownership of the new config dir ("~/.local/share/codeblock") was just fine, properly set to non root users.

So... Running CB 16 as root, it managed to properly save the config files, but... where?

Those files were actually saved to "~/.config/codeblocks"

After chowning "~/.config/codeblocks" to non-root users, everything is fine.

But, this is a sort of a bug, isn't it?
55
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by oBFusCATed on June 22, 2017, 09:20:32 pm »
And "test[1]" is not a too complex expression ...
Why do you think this is not a complex expression?
Are you sure you're python scripts match the version of you c++ standard library you're using?
56
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by BlueHazzard on June 22, 2017, 08:46:25 pm »
if this matters, i have this gdb version: GNU gdb (GDB) 7.10.50.20160130-git
probably i got it from here: http://forums.codeblocks.org/index.php/topic,11301.0.html
57
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by nji on June 22, 2017, 08:40:33 pm »
How can this be?
I downloaded the newest gdb (from link above) and scripts.
And "test[1]" is not a too complex expression ... an error in gdb/ scripts should have shown before.
What about python?
58
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by oBFusCATed on June 22, 2017, 08:33:02 pm »
The problem is in gdb (or the pretty printers). It tells you that it cannot read the value of this expression.
59
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by nji on June 22, 2017, 08:27:15 pm »
It's exactly your code snipplet from above.
I updated the scripts.
test is shown correctly in debugger and in watches, while test[1] is not:

Code: [Select]
[debug]> whatis test[1]
[debug]type = std::vector<double, std::allocator<double> >::reference
[debug]>>>>>>cb_gdb:
[debug]> output test[1]
[debug](__gnu_cxx::__alloc_traits<std::allocator<double> >::value_type &) @0x19de910: <error reading variable>>>>>>>cb_gdb:
[debug]> whatis test
[debug]type = std::vector<double>
[debug]>>>>>>cb_gdb:
[debug]> output test
[debug]std::vector of length 2, capacity 2 = {22.440000000000001, 1.3795933261199322e-306}>>>>>>cb_gdb:
60
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by BlueHazzard on June 22, 2017, 08:05:09 pm »
how does your code looks?
have you updated the scripts?

[edit:] you are right, the space makes no difference...

have you tested my simple example code from the top?
Pages: 1 2 3 4 5 [6] 7 8 9 10