User forums > Using Code::Blocks
Showing vector elements in debugger
stahta01:
--- Quote from: 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?
--- End quote ---
I see two clear solutions to nji "Problem".
1. One his proposed solution to have the next release have an gdb python enabled with what is needed to debug.
2. Stop releasing the mingw version of the CB windows installer.
Tim S.
nji:
While I don't see why your option (2.) helps.
As it shifts the responsiblity for a basic working system to the user (= make it even more unconvenient).
Especially (as the experience in this thread shows) as debug-enabling is not simply done by replacing the binaries.
Even higher hurdles for potential migrants from M$/ beginners.
As the actual tdm package (with python enabled gdb) is used in the nightlys: Are there any experiences?
You set "Problem" in paranthesis.
How shall I take that?
No "Problem" for professional like you? ;)
stahta01:
--- Quote from: nji on June 24, 2017, 03:38:11 pm ---While I don't see why your option (2.) helps.
As it shifts the responsiblity for a basic working system to the user (= make it even more unconvenient).
Especially (as the experience in this thread shows) as debug-enabling is not simply done by replacing the binaries.
Even higher hurdles for potential migrants from M$/ beginners.
As the actual tdm package (with python enabled gdb) is used in the nightlys: Are there any experiences?
You set "Problem" in paranthesis.
How shall I take that?
No "Problem" for professional like you? ;)
--- End quote ---
I do NOT use the debugger very much; so, it is no problem for me.
Maybe I should have put your name in quotes; because I meant to imply it was NOT a CB IDE problem.
But, is instead a CB MinGW packaging problem.
Tim S.
nji:
As I'm quite a newbie to c:b, mingw etc. (a "M$ migrant" ;)) I don't know how the development is organized here.
But - see the experience in the thread - to me it seems not so much a packaging problem, but a kind of configuration problem (as just replacing the debugger from the c:b 16.01package to an actual one does not work, although python enabled and included).
I do not use the debugger very much too - only in the (very very few ;)) cases when something doesn't work as I meant it.
stahta01:
--- Quote from: nji on June 24, 2017, 04:16:38 pm ---As I'm quite a newbie to c:b, mingw etc. (a "M$ migrant" ;)) I don't know how the development is organized here.
But - see the experience in the thread - to me it seems not so much a packaging problem, but a kind of configuration problem (as just replacing the debugger from the c:b 16.01package to an actual one does not work, although python enabled and included).
I do not use the debugger very much too - only in the (very very few ;)) cases when something doesn't work as I meant it.
--- End quote ---
Please read the CB Faqs.
Tim S.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version