Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
...fixed in revision 13360. Sorry about that, I forgot to select one file on the initial commit
2
Now that is is 2023 I wish to follow up because GetName() isn't a coding standard at any shop I've worked at in my 40 years of software development. Method names aren't ProperCase they are camelCase in every shop and API. Was this added in a non-obvious way?
3
You must add whatever file contains WinMain to the linker.

You have used code tags (the #) for the description, please use them (only) for attaching logs and messages instead of using images.
4
General (but related to Code::Blocks) / Compilation Error on CodeBlocks
« Last post by Fredy on Yesterday at 06:02:35 pm »
Code
I am running Code::Blocks version 16.01 on windows 10. The compiler I use is GNU GCC Compiler. Version, I am not sure. When I try to compile a multiple-source file program, it just could not compile. I tried saving both source files on the same directory but it could not work. I have attached the build logs and build messages on this post. Any help?

 
5
indeed something to think about.

7
Help / Re: Assert: "NULL pParser: IdleCallbackHandler* ClgdCompletion..."
« Last post by nore on Yesterday at 12:53:04 am »
Not that I know of. Perhaps only 1 out of 20 launches result in the assertion error showing up; and they persist even less than that--that being appearing after restarting code::blocks.
8
Help / Re: Assert: "NULL pParser: IdleCallbackHandler* ClgdCompletion..."
« Last post by Pecan on September 22, 2023, 11:18:57 pm »
Thanks for reporting.

I'll have a look at it.
Any special way to make it to happen?
9
Using Code::Blocks / debugger can't find file.
« Last post by grayarea56 on September 22, 2023, 08:25:26 pm »
The program runs fine without the debugger.
But when I single step some basic C functions, for instance strcpy, I get this message in the debugger:
Cannot open file: ../sysdeps/x86_64/multiarch/strcpy-avx2.S
Does anyone know what's going on?
Oh, BTW, I'm using WSL Ubuntu under windows 10.
Thanks,
Dan Gray
P.S. here's my test code:

Code
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <stdio.h>
#include <math.h>

int main()
{
    printf("Hello world!\n");
    printf("Sqrt2=%f\n",sqrt(2.0));
    double two = 2.001;
    printf("Sqrt2.001=%f\n",sqrt(two));
    char  goodby[100];
    goodby[10] = 0;
    char hello[100];
    strcpy(hello,"hello");
    hello[5] = 0;
    strcpy(goodby, hello);
    printf("goodby=%s",goodby);
    return 0;
}



10
Help / Assert: "NULL pParser: IdleCallbackHandler* ClgdCompletion..."
« Last post by nore on September 22, 2023, 08:14:56 pm »
Hi there,

I am using code::blocks svn 13344 and have noticed that I occasionally get the following assertion/error upon program launch. Sometimes the error will appear multiple times in a row (with each launch, that is) before launching normally without error. This only occurs perhaps a number of times each week.

NULL pParser: IdleCallbackHandler* ClgdCompletion::GetIdleCallbackHandler(cbProject*)() 662

<press OK>

Fatal assertion error
Assertion failed in IdleCallbackHandler*
ClgdCompletion::GetIdleCallbackhandler(cbProject*) at
C:\Codeblocks\src\plugins\contrib\clangd_client\src\codecompletion\codecompletion.h:665.

pParser && pParser->GetIdleCallbackHandler()

I assume that this is an error regarding the use of the Clangd Client plugin rather than an issue with code::blocks.
The program crashes upon confirmation of the second dialog box regarding the error.
Pages: [1] 2 3 4 5 6 ... 10