Recent Posts

Pages: 1 2 3 [4] 5 6 7 8 9 10
31
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by nji on June 24, 2017, 11:29:38 am »
One should hope, that in the next release of c:b debugging will work.
As in the actual one (16.01) in the packaged mingw the gdb was not python enabled, but in the actual tdm package it is, with everything included that is in need.
So hopefully the devolopers of c:b will have a look that this chain will work, without having to install this and that, patching here and there.
Does this message reach them?
32
General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!
« Last post by richfriz on June 24, 2017, 03:57:50 am »
I am a real person....  :)
33
Help / Re: Upgrading CB 13.12 to 16.01 failed saving config files.
« Last post by stahta01 on June 23, 2017, 06:19:12 pm »
IIRC, an user said they had to run codeblocks from the command line (This was NOT running as root) to get CB to do a good save of CB configs before the unity short-cut would work.

Tim S.
34
Help / Re: Upgrading CB 13.12 to 16.01 failed saving config files.
« Last post by jens on June 23, 2017, 05:26:18 pm »
$HOME/.config/codeblocks is the folder where the config-files shoulf go.
$HOME/.local/share/codeblocks is the folder for user-scripts, -plugins etc.

Something like this is written in the popup-dialog.
So default.conf below .config is expected and correct.

The dialog that pops ups on start and ask for the default-compiler is most likely unrelated to the config-folder change.
If I remember correctly it can also pop up if a compiler search path is invalid in 16.01 or something similar.
35
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by nji on June 23, 2017, 12:19:20 pm »
Thank you for that.  :) :)

You're right ... frustration ... but not mainly because I can't see this f*** test[1],
but because it seems so clear to me that it has to be some kind of "convenient" to have any chance.
That was (to my opinion) the ONLY reason why M$ overcame Linux in the 80ies.
Not quality (for sure), not safety (2xsure), ... but convenience.

See it as learning.. If you know the things behind all this you will get a better programmer

I firmly disagree to that.
I want to focus on my problem, not on the internals of my tools.
To my experience it even keeps you from doing good work if you have to dig too much into side things.

[Edit: Not to talk about the deterent effect on potential beginners]

Please take this thread as my (small) contribution to help.
As long as I'm a newbie.

[Edit:
P.S.
Still one can use printf for debugging.
In times when Radeon RX 470 GPUs are used for making Bitcoins,
with c:b we are practicising ... no, not agile ...but ... amish software development and toolchain config.   ;) ;)
SCNR. NOT meant to offend.]
36
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by BlueHazzard on June 23, 2017, 12:08:57 pm »
@ollydbg:
does it make sense to provide the python dll within your gdb download? Are there dependencies to other dlls (from python27.dll to other) too?
What if there is a python27.dll in the bin folder and one in the system folder? What version gets picked?
I see the frustration of the OP and i would like to do something against it...
37
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by nji on June 23, 2017, 11:52:26 am »
I won't install python. (Reason for this ... see above).

If someone is trying to get rid of the M$ trap, you may tell him:
No, the debugger doesn't work at codeblock.
This is not our problem.
But you can try to install this & that to your system, and see what it makes to it.

This thinking is exactly what makes M$ success. Greetings.
38
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by BlueHazzard on June 23, 2017, 11:05:56 am »
Quote
But ... as it seems ... that way didn't work ... at least at me.
does it work after installing python? If not what is the error you are getting?
39
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by nji on June 23, 2017, 10:46:46 am »
You're so right ... and a bit of self thinking and read what I wrote would keep you from being impolite.
40
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by BlueHazzard on June 23, 2017, 10:35:18 am »
Quote
What I mean: If one installs c:b ... is it necessary to install python before, if gdb is python-enabled?
codeblocks does not need python... gdb needs python. This are two separate projects. Codeblocks can not provide support for all things... And if codeblocks has to ship dlls for all possibly needed additional programs, the purpose of dlls is circumvented...

I had python installed previously for using it to program in python, so i don't had to install it. A bit of self thinking and googling solves this kind of problems in 2 sek.

i updated my previous post.
Pages: 1 2 3 [4] 5 6 7 8 9 10