User forums > Help
"No source file named " problem while debugging
Kayl:
Would it be possible for C::B team to post a message on this thread when Ramazan Kartal's patch will be used in a nightly build as I am in the same situation and dying to be able to debug my static lib without having to switch to VC just for that.
May I also use this message to ask how you guys deal with dependencies with your static lib ?
My app (.exe) depends on the static lib. The app project is the current one. Each time I build the app when the static lib sources have changed, the .a is generated just fine but the building of the app itself is more than random. Most of the time it says it is "uptodate" (when it's not) and doesn't link (use) the new .a
mandrav:
--- Quote from: kayl ---Would it be possible for C::B team to post a message on this thread when Ramazan Kartal's patch will be used in a nightly build
--- End quote ---
When it has been checked that it works as expected across most platforms.
--- Quote from: kayl ---May I also use this message to ask how you guys deal with dependencies with your static lib ?
My app (.exe) depends on the static lib. The app project is the current one. Each time I build the app when the static lib sources have changed, the .a is generated just fine but the building of the app itself is more than random. Most of the time it says it is "uptodate" (when it's not) and doesn't link (use) the new .a
--- End quote ---
Nothing is random inside C::B (well, maybe except the $COIN and $RANDOM variables ;)).
To accomplish what you want, go to your executable target's properties, click the "External dependencies" button and add the static lib's filename there.
diazdh:
Hi everyone,
Thanks for the great work, CB is a really nice and powerful development tool.
The project I'm working on is also affected by the problem that is the subject of this thread (I have already written a follow-up to the bug #008949 at BerliOS with some details about that).
Ramazan Kartal's patch solves this problem using absolute paths to set the breakpoints. However it's possible, in case that it happens to be necessary, to restrict the use of absolute paths to the construction of the gdb search path.
Could you please tell me where is the apropriate place to post the details of that approach? I hope they could be useful for the development process of the debugger plugin or maybe for some other component of Code:Blocks.
Thanks in advance,
Dhionel Diaz
MortenMacFly:
--- Quote from: diazdh on December 09, 2006, 10:47:28 pm ---Ramazan Kartal's patch solves this problem using absolute paths to set the breakpoints. However it's possible, in case that it happens to be necessary, to restrict the use of absolute paths to the construction of the gdb search path.
--- End quote ---
Please notice this, too: http://forums.codeblocks.org/index.php?topic=4850.msg38322#msg38322
With regards, Morten.
nanyu:
today I update the gdb to "6.3 -2" (from 5.3)
I found the "No source file named" come back if the proejct path include a space char.
>>>>>>cb_gdb:
> break "C:/aa bb/main.cpp:7" <-- NOTE: there is a space between "aa" and "bb".
No source file named C:/aa bb/main.cpp.
Breakpoint 2 ("C:/aa bb/main.cpp:7) pending.
BUT it I create a project in a "aa_bb", the gdb work fine.
-------------------
c::b 5731
windows xp
gcc 4.2.2
gdb 6.3-2
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version