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

wxWidgets 3.0.0 released!

<< < (7/8) > >>

oBFusCATed:
I'm able to reproduce the problem using the minimal sample in wx30's relatively latest git.

Here is the patch:

--- Code: ---diff --git a/samples/minimal/minimal.cpp b/samples/minimal/minimal.cpp
index a78e462..dc0709a 100644
--- a/samples/minimal/minimal.cpp
+++ b/samples/minimal/minimal.cpp
@@ -123,6 +123,7 @@ bool MyApp::OnInit()
     // few common command-line options but it could be do more in the future
     if ( !wxApp::OnInit() )
         return false;
+//    wxExecute(wxT("gcc -dumpversion"), wxEXEC_SYNC);//|wxEXEC_NOEVENTS);

     // create the main application window
     MyFrame *frame = new MyFrame("Minimal wxWidgets App");
@@ -197,4 +198,5 @@ void MyFrame::OnAbout(wxCommandEvent& WXUNUSED(event))
                  "About wxWidgets minimal sample",
                  wxOK | wxICON_INFORMATION,
                  this);
+    wxExecute(wxT("gcc -dumpversion"), wxEXEC_SYNC);//|wxEXEC_NOEVENTS);
 }

--- End code ---

In order to reproduce this.
1. Apply the patch
2. Create a project for the minimal sample
3. Try to debug the sample using C::B

Results:
1. The sample hang at both wxExecute calls
2. The gcc executable is left as zombie process, so something doesn't close correctly
3. wxExecute never exits

I've not yet contacted the wx devs, but I'll do it as soon as I gather more data. Hopefully it is not reproducable on newer linuxes only.


@Jens and any dev or Linux user willing to try: Could you try to reproduce this problem?

BlueHazzard:
here on Linux Mint 15 your example works with latest wxWidgets svn. No blocked or zombie process in debugging or running...
gcc 4.7.3
gdb (GDB) 7.5.91.20130417

greetings

MortenMacFly:

--- Quote from: stahta01 on January 12, 2014, 01:51:11 am ---Since we are using wx3.0 propgrid; we should NOT have the one in SDK in the search list.

--- End quote ---
That is true... and applied in trunk. Thank you!

Uskok:

--- Quote from: oBFusCATed on January 12, 2014, 07:56:04 pm ---
--- Quote from: Uskok on January 12, 2014, 07:34:15 pm ---Try to disable CC, it corrupted something very badly.

--- End quote ---
This problem happens during startup, I doubt it is related to CC...

Edit: It is not, I've tried with disabled CC.

--- End quote ---
I wrote suggestion because under Linux (RH 6.4, wx30, sources from trunk) I had strange behavior of CodeBlocks. I was able to open project and after start compile only the messages from first file was omitted and the CB stops to response.  With disabled CC compilation process was OK.

oBFusCATed:
Uskok: You are experiencing the same problem. But because the bug is a race condition or something like that is not 100% reproducible.

BlueHazzard: Can you post the versions of kernel, gtk+, glibc, glib?

Navigation

[0] Message Index

[#] Next page

[*] Previous page