Recent Posts

Pages: 1 2 [3] 4 5 6 7 8 ... 10
21
Development / Re: C::B EOF?
« Last post by gtafan on April 23, 2019, 03:34:59 pm »
Quote from: stahta01 on April 21, 2019, 05:43:59 pm
Quote from: gtafan on April 21, 2019, 05:33:51 pm
So any chance to see the new CodeBlocks version this year? I mean that nightly build stuff is just something for hardcore CB users.

No, it is for people who wish to help this project improve.

Tim S.
Sorry but canīt completly agrre, itīs not enough to wish to do something, you need to have some skills in doing it and not everibody is familiar with that compiler, linker and build stuff.
22
Plugins development / Re: [New plugin] cbSystemView for embedded development
« Last post by oBFusCATed on April 23, 2019, 08:29:12 am »
What do you mean by proxy program? On windows any gdb which supports python is setup to start two executables gdb and gdb_orig... This causes lots of problems...
23
Using Code::Blocks / Re: How do I turn off bare std keyword highlight when I don't have using namespace?
« Last post by oBFusCATed on April 23, 2019, 08:26:40 am »
No this won't going to work. Not sure if it will work if you put std::cin there.
24
Using Code::Blocks / Re: How do I turn off bare std keyword highlight when I don't have using namespace?
« Last post by EuphoricCatface on April 23, 2019, 05:01:48 am »
Thank you for your answer. I have seen your reply but did not have a chance to try it out.
My environment was not working for other reason :P
Anyways. I assume, roughly, I could erase "std" from set 2 and put "std::" for any other keywords in the set?
Would that make, say, "std::cin" highlighted but not "cin" alone?
25
General (but related to Code::Blocks) / Re: Forum in https?
« Last post by BlueHazzard on April 22, 2019, 11:28:45 pm »
LetsEncrypt is free.... so no cost for the certificate... the additional cost are pure electricity/bandwidth costs, that you have because of ssl...

[edit:] sry, i misread your comment...
Quote
If you don't want to use LetsEncrypt
26
Plugins development / Re: [New plugin] cbSystemView for embedded development
« Last post by BlueHazzard on April 22, 2019, 11:25:41 pm »
The problem with the debugger i had, by not be able to send a ctrl+c to the gdb trough codeblocks was because i run codeblocks with codeblocks... If i run codeblocks directly i am able to send the ctrl+c....

Not working:
Code: [Select]
codeblocks->codeblocks->arm_gdb->arm_gdb_serverworking:
Code: [Select]
codeblocks->arm_gdb->arm_gdb_serverthis has probably something to do with the executable group... I think at some time we need to introduce a proxy program for gdb.... (also the 32bit <-> 64 bit thing would be solved by this) but this is for later...
27
General (but related to Code::Blocks) / Re: Forum in https?
« Last post by FossHub on April 22, 2019, 11:21:06 pm »
If you don't want to use LetsEncrypt, there are also cheaper options, something like $5-6 per year or $23 per five years. I don't think you will find a lower price. If there's any admin interested please PM and we can help.
28
Plugins development / Re: [New plugin] cbSystemView for embedded development
« Last post by BlueHazzard on April 22, 2019, 11:06:13 pm »
Ok, i tested it now and it seems to work on windows 7.

The plugin still needs some tweaks, but the api is fine and should work!

great!
29
Help / Re: Malloc() / Heap issue with debug build target
« Last post by BlueHazzard on April 22, 2019, 10:54:37 pm »
So it crashes also if no watches are enables and the watch view is empty?

The debug log is not about the warnings, but about the difference between release and debug build, so you should post a build log of the release build and the debug build, so we can compare the compiler flags. But this is only for the future, or for other reader, i do not suspect that this is the problem here...

Have you checked if the len variable has a reasonable size?
Code: [Select]
if (!GetNextCode32(&len)) {
    PrintError(14, NULL, "ReadString()");
    return(NULL);
  }

  /* create space on heap */
  if ((str = (char *) malloc(len*sizeof(char))) == NULL) {
using uninitialized variables is never the best idea, and no range checking for a malloc input also not....
30
Help / Re: Malloc() / Heap issue with debug build target
« Last post by Marnix on April 22, 2019, 10:44:30 pm »
Watch variables was enabled. I turned it off, but without success.

The crash reason is a SIGSEGV.

I F7-ed through the code and I narrowed it down to this for loop:

Code: [Select]
    for (i=0; i<nr_of_lflags; i++) {
      if ( ((loc_flag_dbug[i]).name = ReadString()) == NULL)
        return(ERROR);

      if (!GetNextCode32(&(loc_flag_dbug[i]).owner))
        return(ERROR);
    }
The ReadString() function (listed in the opening post) has a malloc() that crashes.

loc_flag_dbug is an array of structs wirh a char* and an int32_t, this array is malloced as well with length nr_of_lflags:


Code: [Select]
    /* Malloc() space for local flags debug info. */
    if ((loc_flag_dbug = (debugInfo *) malloc(nr_of_lflags*sizeof(debugInfo))) == NULL) {
      PrintError(15, NULL, "local flags debug info");
      return(ERROR);
    }
Strange thing is that the iteration of the loop when it crashes differs. This afternoon after I restarted my computer it did not crash at all. Now, after I saw your post I tried again and now it crashes again.
Pages: 1 2 [3] 4 5 6 7 8 ... 10