User forums > General (but related to Code::Blocks)

wxWidgets 3.0.0 released!

<< < (8/8)

BlueHazzard:
libgtk 3.6.4-0ubuntu8
glibc 2.17
glib 2.36
kernel 3.8.0 (wow quite old oO)

greetings

oBFusCATed:
BlueHazzard:
Could you try to rebuild wx30 with the --enable-debug configure option and try again to debug the minimal sample.
I've just rebuild my wx30 without using this option and C::B starts inside C::B without problems.
I can debug the minimal sample project, too.

BlueHazzard:
with --enable-debug it is a different behaviour:
1) if i run it with gdb (with a break point on wxExecute) it works, and the process exits without error
1.1) if i run it with gdb step by step it blocks at utilsunix.cpp:853 in
 
--- Code: ---return BlockUntilChildExit(execData);
--- End code ---
and i get a zombie gcc process
1.2) if i run it with gdb step by step without wxEXEC_NOEVENTS it blocks at utilsunix.cpp:862 and i get a zombie gcc process

in both cases i had to step until this line. If i only run with the debugger there was no error...

3.1) if i run it without debugger with wxEXEC_NOEVENTS i get a zombie gcc process
3.2) if i run it without debugger without wxEXEC_NOEVENTS the process ends without error

greetings

oBFusCATed:
Thank you for your experiments. One question what do you mean by gdb: standalone gdb in terminal or gdb run by C::B's debugger plugin?

BlueHazzard:
gdb in C::B plugin...
but there were no errors on the c::b site. The log was ok and also the application responded...
greetings

Navigation

[0] Message Index

[*] Previous page