News:

When registered with our forums, feel free to send a "here I am" post here to differ human beings from SPAM bots.

Main Menu

C::B freezes completely with macros in tools menu (?)

Started by MortenMacFly, January 16, 2006, 02:20:29 PM

Previous topic - Next topic

MortenMacFly

What I did: I've added 2 tools to the "Tools" menu: SciTE and Windows Notepad. I've setup the tools to apply the ${ACTIVE_EDITOR_FILENAME} "macro" as parameter and to be launched in the ${PROJECT_DIR}. Whenever I have a file opened and try to run one of these tools C::B freezes completely and uses 100% CPU and I have to kill C::B with the task-manager. I did this before (last year...) and it was working properly for ages. I don't know if and when this got broken or whether it is a problem of my fresh intallation. Coudl someone verify, please?
Morten.
Edit: WinXP, C::B revision 1767 (and a few before), wxWidgets 2.6.2 (unicode).
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

killerbot

idea : write a little program that dumps it's command line arguments, to see what comes in.
Maybe quotes issues, or unicode issues ??

[edit] : and use that program as the tool

thomas

It seems to happen with any kind of variable in any of the tool config dialog's field, not just the two you tried.
So far, no idea why, though.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

MortenMacFly

Good idea! But: I tried, but it's not the tool that is the reason. The tool doesn't even gets launched (I verified using sysinternals filemon)...
So I think it must be before the call inside C::B. Could you try to add Notepad yourself? Does it work for you? Thanks, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

MortenMacFly

Quote from: thomas on January 16, 2006, 02:35:40 PM
So far, no idea why, though.
Ooops, we were both writing at the same time. So ignore my message before... Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

thomas

As soon as this darn raytracer stops hijacking the CPU, I'll try to find out some more, but currently Code::Blocks takes 3 minutes to start up...
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

mandrav

Be patient!
This bug will be fixed soon...

MortenMacFly

Quote from: mandrav on January 16, 2006, 02:56:08 PM
Fixed now.
...I can confirm this. Thanks a lot - this was again very faaaast (as usual ;-)). Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]