Recent Posts

Pages: 1 2 [3] 4 5 6 7 8 ... 10
21
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by nji on June 24, 2017, 06:39:05 pm »
Banned?  :-\

Will you come with me?


Usually I don't explain my points ...
But for you I will do an exception:
Yes, I will take you for serious ...
... as soon as you do mature.
I always tried to explain/ to give reason for what I wrote above.
I can't imagine of anything more revealing weakness than the threat of a bann.
Oh man ...
22
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by stahta01 on June 24, 2017, 06:22:06 pm »
Quote from: nji on June 24, 2017, 05:11:01 pm
What a pity for you.  :)

So you will never understand why to point blanket to the FAQ isn't very sensible after I explained in detail.

But maybe you're right ... it looks to be a "waste of time" with you.

Please read the rules before you are banned!
http://forums.codeblocks.org/index.php/topic,9996.0.html
23
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by nji on June 24, 2017, 05:11:01 pm »
What a pity for you.  :)

So you will never understand why to point blanket to the FAQ isn't very sensible after I explained in detail.

But maybe you're right ... it looks to be a "waste of time" with you.
24
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by stahta01 on June 24, 2017, 04:36:03 pm »
Quote from: nji on June 24, 2017, 04:22:53 pm
As soons as I've finished "The Three Towers".

I am going to ignore you from now on as a waste of time.

Tim S.
25
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by nji on June 24, 2017, 04:22:53 pm »
As soons as I've finished "The Three Towers".
26
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by stahta01 on June 24, 2017, 04:19:22 pm »
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.

Please read the CB Faqs.

Tim S.
27
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by 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.

28
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by stahta01 on June 24, 2017, 03:41:24 pm »
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?  ;)

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.
29
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by 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?  ;)
30
Using Code::Blocks / Re: Showing vector elements in debugger
« Last post by stahta01 on June 24, 2017, 03:00:32 pm »
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?

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.
Pages: 1 2 [3] 4 5 6 7 8 ... 10