Recent Posts

Pages: 1 2 3 4 [5] 6 7 8 9 10
41
Isn't there the annoying dialog api?And there should be a subfunction for MessageBox that creates a hide able dialog.. I don't know if it is possible to log it instead...
If this is not a wx dialog it should be pretty easy...
42
Using Code::Blocks / Re: How to tell Code::Blocks where wxWidgets is?
« Last post by spflanze on August 11, 2018, 09:11:09 am »
Because on page:
https://wiki.wxwidgets.org/Wx-Config
It is the back tick that is used. Changing to the apostrophe was an experiment that failed to get it compiled, although the error was different.

I used the back tick in the flags, but I see in the build log enclosing apostrophes in the -pthread option's parameter. Should that be?
43
Probably. Many people want to be able to disable various info windows. So a config system for those might be useful.
44
Is it possible to translate those message box(dialog) to some logs, because the message box is so annoying, while I can live with the logs. ;)
45
Here is my suggestion:
1, you can write a simple script(maybe using python) file which replace the source file paths in the cbp(you may first create a cbp template).
2, you can write a simple cmake, and let cmake generate all the cbp files.

I think method 1 is easier.
46
Using Code::Blocks / Re: Help debugging with GDB...
« Last post by PaulR on August 10, 2018, 11:58:26 pm »
Aaahhh, success!! In addition to not showing info symptoms, the exe was crashing when I tried setting a breakpoint (it would pause, but no highlighting of the line, no info or other sign that the breakpoint was reached) and tried continuing.

It turns out that the issue was I was using the 64 bit GDB in MSYS2. Setting the debugger to use the 32 bit one works!

Thanks for helping eliminate possibilities!
47
Using Code::Blocks / Re: Help debugging with GDB...
« Last post by oBFusCATed on August 10, 2018, 10:37:50 pm »
Yes, it should be possible to debug if you have symbols only for part of your app. Keep in mind that mixing dlls compiled with vc++ and mingw doesn't work well, because gdb doesn't know how to read the symbols produced by vc++.
48
Using Code::Blocks / Re: Help debugging with GDB...
« Last post by PaulR on August 10, 2018, 08:43:02 pm »
Hmm, it looks like I need to make a full Qt debug build to get some files to make the exe build correctly in debug. I'm not interested in debugging the main exe though, just the code for a few of the dlls. Is this possible?
49
Using Code::Blocks / Re: Help debugging with GDB...
« Last post by PaulR on August 10, 2018, 08:17:08 pm »
Thanks very much for the reply.

1: I'll check the build scripts for this.
2: Yes, everything is fine with debugging (breakpoints/call stack)
3: The modules I am interested in changing code for all have read symbols (no [ * ] next to them).

I checked "Debug->Information->Targets and files" and for the local exec file, there is a long list of addresses in the results - including the entry point and the modules checked in #3, so this probably indicates something is wrong with that file too I assume.
50
Generally it is hard to make this work.
What I do these days when I want to debug programs started by some complex scripts is to place code looking something like this in my application:
Code: [Select]
system("codeblocks --dbg-config=<my config> --dbg-attach=<mypid>");
sleep(2); // just to make sure attaching works
I put this somewhere around the beginning of main.
I start my application in a terminal and then the debugger attaches automagically.
For this to work you need really recent night/trunk build of codeblocks.

Can you reproduce "Starting the debuggee failed: No executable file specified." in a simple project you can share with us? I'm interested to try to make it less confusing or make it work if possible.
Pages: 1 2 3 4 [5] 6 7 8 9 10