The 28 January 2007 build is out.

[killerbot]

@
indigo0086
skirby
pasgui


Someone mentioned a cause, he had '[' and/or ']' in his path. Our regular expressions used for the parsing of the compiler output didn't support that. I am working on a fix, should be available this evening. I will write a special post about it.
Could you check if you had one of the following characters in your path (to the project or source files) :
(
)
{
}
[
]

[gd_on]

Small bug I discovered with this nightly but probably not new.
Here a small C program, in a project (test.cbp, under windows XP and Win 2000) :

#include <stdio.h>
#include <stdlib.h>

int ii=11 ;

void sub1 ( )
{
    int iiloc ;

    iiloc = 2*ii ;
    printf("%d %d\n",ii,iiloc) ;
}

int main()
{
    printf("Hello world!\n");
    sub1() ;
    return 0;
}

This program works but :
If within sub1 I right click on the variable ii then click on Find declaration of ii, it works: the cursor is on ii declaration.
But if I right click on iiloc (in iiloc = 2*ii or within the printf), I obtain a message declaration "Warning Not found : iiloc".
On a more complex project, even some global variables are not found (but not all).

gd_on

[skirby]

@
indigo0086
skirby
pasgui


Someone mentioned a cause, he had '[' and/or ']' in his path. Our regular expressions used for the parsing of the compiler output didn't support that. I am working on a fix, should be available this evening. I will write a special post about it.
Could you check if you had one of the following characters in your path (to the project or source files) :
(
)
{
}
[
]

Hello killerbot,

You are absolutly right.
In fact, I have a # in my folder name.
If I remove it, it works 

[killerbot]

woops, another one that add to the list

[skirby]

You can also add the character ~ and =
I suppose there are more character which cause problem.

More, if the path contains an $ character, I have the following error message:

-------------- Build: Debug in Test ---------------
Compiling: main.c
mingw32-gcc.exe: D:\Test\main.c: No such file or directory
mingw32-gcc.exe: no input files
Process terminated with status 1 (0 minutes, 0 seconds)
0 errors, 0 warnings

The real folder name is: D:\Test$1\

I hope you could correct it.

[indigo0086]

thank's for working on that killerbot.  I only put the words in braces because I have a lot of folders in my documents and want to put all frequently used folders sorted at the top.

[killerbot]

You can also add the character ~ and =
I suppose there are more character which cause problem.

More, if the path contains an $ character, I have the following error message:

-------------- Build: Debug in Test ---------------
Compiling: main.c
mingw32-gcc.exe: D:\Test\main.c: No such file or directory
mingw32-gcc.exe: no input files
Process terminated with status 1 (0 minutes, 0 seconds)
0 errors, 0 warnings

The real folder name is: D:\Test$1\

I hope you could correct it.

the $ sign is more difficult, your problem is not the same on what I am working on right now. I am fixing the output of the compiler, you have a problem on the input side to the compiler. CB support macro replacing and macros start with $ --> CB tries to replace the $1, which has no value so it ends up being removed (replaced by nothing).
@Thomas, Yiannis --> any ideas on this issue ??

In the meantime I will support the $sign on the output side ;-)

[Jordar]

<Can't Debug Issue>

I did some more research by rolling back to the last version that I can build and debug with.  This is on Jan 10th.  It seems that the Debugger here uses the truncated path names instead of the full names.  ("Docume~1" instead of "Documents and Settings").  Is there some way around this?  I don't see an option to change this in the debugger settings.

thanks,
Jordar

[indigo0086]

I'm not sure if this is normal but will the debugger enter from a breakpoint within a header file, or does it only enter through source files?

[Pecan]

I'm not sure if this is normal but will the debugger enter from a breakpoint within a header file, or does it only enter through source files?

Yes, it can stop at a breakpoint in a header file. When I'm debugging a header that contains something like:

Code Select Expand


void MyClass::thisfunc(int intVar)
    {m_someVar = intVar;}


I can put a breakpoint on the m_someVar=intVar; statement.

[indigo0086]

Hmm, when I put a breakpoint in a function in a header file (which has to have been called by main), it skips over it and ends.  I get this message in the debugger.

Setting breakpoints
Debugger name and version: GNU gdb 6.3
No source file named E:/Documents/COP 4338 Programming III Projects/project1/urlSearcher.h.
Breakpoint 1 ("E:/Documents/COP 4338 Programming III Projects/project1/urlSearcher.h:31) pending.
Program exited normally.
Debugger finished with status 0

it just skipped over the breakpoint.

[Pecan]

Hmm, when I put a breakpoint in a function in a header file (which has to have been called by main), it skips over it and ends.  I get this message in the debugger.

Setting breakpoints
Debugger name and version: GNU gdb 6.3
No source file named E:/Documents/COP 4338 Programming III Projects/project1/urlSearcher.h.
Breakpoint 1 ("E:/Documents/COP 4338 Programming III Projects/project1/urlSearcher.h:31) pending.
Program exited normally.
Debugger finished with status 0

it just skipped over the breakpoint.

Take the spaces out of the filenames and see if it works.

Note: Breakpoints in constructors/destructors do not work.

cf: See the note at the bottom of:
//-- Debugging
    Debugging with CodeBlocks

[indigo0086]

Yup that works.  Guess I have to change all my file hierarchy  :lol:

[Jordar]

But I USED to be able to have spaces since the debugger used short names.  Is this a bug? Why were the debugger settings changed to long path names?

[indigo0086]

Also what font is that used in the debugging example?\


Edit: I also found when exporting to rtf, it does not show any word delimited by whitespace after an escape indicator.  so

Code Select Expand

cout << "\nhello world";

will show as

Code Select Expand

cout << "world";

on the exported document