Author Topic: 17.xx, RC1 has arrived  (Read 1647 times)

Offline windwalker

  • Single posting newcomer
  • *
  • Posts: 2
Re: 17.xx, RC1 has arrived
« Reply #15 on: December 06, 2017, 12:24:40 pm »
What happens if you use a debugger?
This happens.
Code: [Select]
C:\Program Files (x86)\CodeBlocks>gdb codeblocks.exe
GNU gdb (GDB) 7.9.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from codeblocks.exe...(no debugging symbols found)...done.
(gdb) run
Starting program: C:\Program Files (x86)\CodeBlocks\codeblocks.exe
[New Thread 11084.0x2454]
warning: `C:\WINDOWS\SYSTEM32\ntdll.dll': Shared library architecture i386:x86-64 is not compatible with target architecture i386.
warning: `C:\WINDOWS\System32\wow64.dll': Shared library architecture i386:x86-64 is not compatible with target architecture i386.
warning: `C:\WINDOWS\System32\wow64win.dll': Shared library architecture i386:x86-64 is not compatible with target architecture i386.
warning: Could not load shared library symbols for WOW64_IMAGE_SECTION.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for WOW64_IMAGE_SECTION.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for WOW64_IMAGE_SECTION.
Do you need "set solib-search-path" or "set sysroot"?
warning: `C:\WINDOWS\System32\wow64cpu.dll': Shared library architecture i386:x86-64 is not compatible with target architecture i386.
[New Thread 11084.0x2008]
[New Thread 11084.0x638]
[New Thread 11084.0x1f18]
[New Thread 11084.0xa6c]
[New Thread 11084.0x1a28]
[New Thread 11084.0x265c]
[New Thread 11084.0x1760]
[New Thread 11084.0x23b8]
[New Thread 11084.0x1f38]
[New Thread 11084.0x2814]
[New Thread 11084.0x12ac]
[Thread 11084.0x12ac exited with code 0]
[New Thread 11084.0x444]
[Thread 11084.0x444 exited with code 0]
[New Thread 11084.0x1300]
[Thread 11084.0x1300 exited with code 0]

Program received signal SIGSEGV, Segmentation fault.
0x0000002b in ?? ()
(gdb)

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1585
Re: 17.xx, RC1 has arrived
« Reply #16 on: December 06, 2017, 01:27:30 pm »
Got the same crash with the empty back trace. Currently i try to rebuild wxWidgets git and codeblocks and to get a real back trace. Can you tell me what wxWidgets version do you used? There is no tag with wx311 or similar...

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1585
Re: 17.xx, RC1 has arrived
« Reply #17 on: December 06, 2017, 02:28:25 pm »
I compiled all by my self and can not reproduce the crash.

Windows 7 64 bit

gcc version 5.1.0 (tdm-1)

wxWidgets 204bc3c887a172c30c490e15de4f1cea66f4230e (debug build)
Codeblocks 3d48746051e14fc8a90d0384681b396ec8a4a80f ( git-svn-id: https://svn.code.sf.net/p/codeblocks/code/branches/release-17.xx@11244 ) (debug build)

i try release now
[Edit] Same setup, but wxWidgets build as release crashes. But no back trace...
Code: [Select]
#0 0x6440bc90 wxCommandEvent::GetString() const() (wxWidgets\lib\gcc_dll\wxmsw311u_gcc_custom.dll:??)

[Edit2:] Core plugins and app work without crash, so it is some plugin crashing

[Edit3:] Thread search is (one of) the culprit
« Last Edit: December 06, 2017, 04:00:18 pm by BlueHazzard »

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1585
Re: 17.xx, RC1 has arrived
« Reply #18 on: December 06, 2017, 04:10:31 pm »
Ok, here is (one of) the crash:

src\plugins\contrib\ThreadSearch\DirectoryParamsPanel.cpp:71
Code: [Select]
   
m_pMask = new wxComboBox(this, controlIDs.Get(ControlIDs::idSearchMask), wxT("*.*"),
                             wxDefaultPosition, wxDefaultSize, 0, choices, wxCB_DROPDOWN|wxTE_PROCESS_ENTER);

I can not find out, why it crashes. All parameter seem to be fine and valid. The crash is in the wxWidgets library, but it does not happen in debug build...

[edit:] this is some race condition. i removed all combobox things and still get the same crash, but on a later point

Any ideas?
« Last Edit: December 06, 2017, 05:40:34 pm by BlueHazzard »

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 4992
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: 17.xx, RC1 has arrived
« Reply #19 on: December 07, 2017, 01:20:41 am »
Ok, here is (one of) the crash:

src\plugins\contrib\ThreadSearch\DirectoryParamsPanel.cpp:71
Code: [Select]
   
m_pMask = new wxComboBox(this, controlIDs.Get(ControlIDs::idSearchMask), wxT("*.*"),
                             wxDefaultPosition, wxDefaultSize, 0, choices, wxCB_DROPDOWN|wxTE_PROCESS_ENTER);

I can not find out, why it crashes. All parameter seem to be fine and valid. The crash is in the wxWidgets library, but it does not happen in debug build...

[edit:] this is some race condition. i removed all combobox things and still get the same crash, but on a later point

Any ideas?

I believe it is a compiler optimization bug, I reported before.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1585
Re: 17.xx, RC1 has arrived
« Reply #20 on: December 07, 2017, 08:40:13 am »
I believe it is a compiler optimization bug, I reported before.
Makes sene, because of only triggering by non debug build, but how it comes to only get triggered by the thread search plugin?

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 4992
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: 17.xx, RC1 has arrived
« Reply #21 on: December 07, 2017, 03:51:25 pm »
I believe it is a compiler optimization bug, I reported before.
Makes sene, because of only triggering by non debug build, but how it comes to only get triggered by the thread search plugin?
No idea, I see such kinds of bug several times.
BTW: my reports are here: Threadsearch plugin cause crash when initilized (wx3.1,C::B svn head), I believe this bug can be reproduced by a wx sample code. But no idea how to find such minimal sample. :(
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.