Author Topic: The 22 March 2014 build (9744) is out.  (Read 66052 times)

ToApolytoXaos

  • Guest
Re: The 22 March 2014 build (9744) is out.
« Reply #60 on: May 07, 2014, 10:03:06 pm »
@jens: Update about the crashing issue; it remains the same, but I think I got an idea of why it would crash (I hope i'm wrong with this):

Code: [Select]
(gdb) run -d -v
Starting program: /usr/bin/codeblocks -d -v
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe8303700 (LWP 16872)]
[New Thread 0x7fffe7b02700 (LWP 16873)]
[New Thread 0x7fffe7301700 (LWP 16874)]
[New Thread 0x7fffd8533700 (LWP 16907)]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) thread apply all bt

Thread 5 (Thread 0x7fffd8533700 (LWP 16907)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007ffff58ee653 in wxConditionInternal::Wait() () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#2  0x00007ffff58ef1a8 in wxSemaphoreInternal::Wait() () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#3  0x00007fffdcfb4a62 in ClassBrowserBuilderThread::Entry (this=0x446d000) at classbrowserbuilderthread.cpp:193
#4  0x00007ffff58ef983 in wxThreadInternal::PthreadStart(wxThread*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#5  0x00007ffff3187062 in start_thread (arg=0x7fffd8533700) at pthread_create.c:312
#6  0x00007ffff2492bfd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7fffe7301700 (LWP 16874)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007ffff58ee653 in wxConditionInternal::Wait() () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#2  0x00007ffff58ef1a8 in wxSemaphoreInternal::Wait() () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#3  0x00007ffff779984a in BackgroundThread::Entry (this=0xefbb48) at ./backgroundthread.h:152
#4  0x00007ffff58ef983 in wxThreadInternal::PthreadStart(wxThread*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#5  0x00007ffff3187062 in start_thread (arg=0x7fffe7301700) at pthread_create.c:312
#6  0x00007ffff2492bfd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fffe7b02700 (LWP 16873)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007ffff58ee653 in wxConditionInternal::Wait() () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#2  0x00007ffff58ef1a8 in wxSemaphoreInternal::Wait() () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#3  0x00007ffff779984a in BackgroundThread::Entry (this=0xefbb10) at ./backgroundthread.h:152
#4  0x00007ffff58ef983 in wxThreadInternal::PthreadStart(wxThread*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#5  0x00007ffff3187062 in start_thread (arg=0x7fffe7b02700) at pthread_create.c:312
#6  0x00007ffff2492bfd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fffe8303700 (LWP 16872)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007ffff58ee653 in wxConditionInternal::Wait() () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#2  0x00007ffff58ef1a8 in wxSemaphoreInternal::Wait() () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#3  0x00007ffff779984a in BackgroundThread::Entry (this=0xefbad8) at ./backgroundthread.h:152
#4  0x00007ffff58ef983 in wxThreadInternal::PthreadStart(wxThread*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#5  0x00007ffff3187062 in start_thread (arg=0x7fffe8303700) at pthread_create.c:312
#6  0x00007ffff2492bfd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7ffff7fb0a00 (LWP 16370)):
#0  0x0000000000000000 in ?? ()
#1  0x00007ffff61fea44 in wxAppBase::SendIdleEvents(wxWindow*, wxIdleEvent&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#2  0x00007ffff61fee74 in wxAppBase::ProcessIdle() () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#3  0x00007ffff6179e91 in ?? () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#4  0x00007ffff33e4ce5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007ffff33e5048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007ffff33e530a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007ffff52f9147 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#8  0x00007ffff618d36a in wxEventLoop::Run() () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#9  0x00007ffff61fec1c in wxAppBase::MainLoop() () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#10 0x00000000004484fb in CodeBlocksApp::OnRun (this=0x7d3bb0) at app.cpp:818
#11 0x00007ffff589df7d in wxEntry(int&, wchar_t**) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#12 0x000000000043b962 in main (argc=3, argv=<optimized out>) at app.cpp:278
(gdb) continue
Continuing.

Program received signal SIGABRT, Aborted.
0x00007ffff23e23a9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56      ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) continue
Continuing.
[Thread 0x7fffd8533700 (LWP 16907) exited]
[Thread 0x7fffe8303700 (LWP 16872) exited]
[Thread 0x7ffff7fb0a00 (LWP 16370) exited]
[Thread 0x7fffe7b02700 (LWP 16873) exited]

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb)

While I am in xterm or whatever terminal that might be, and call Code::Blocks via GDB and keep event's attention to terminal, it works fine. If I run Code::Blocks inside GDB and use alt-TAB to switch to Code::Blocks' splash screen, it would work until the final GUI frame drawing on the right sidebar; that is where it breaks for some reason.

Is there a (painfully, thorough) way to debug UI layer on top of layer? I really am curious to see whether this issue is
  • a Code::Blocks bug
  • a wxGTK bug or
  • a lib64 issue for some reason.

Cheers

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11267
    • Travis build status
Re: The 22 March 2014 build (9744) is out.
« Reply #61 on: May 07, 2014, 11:35:21 pm »
It is a bug in the splash screen... Use -ns and you won't see it.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 2096
Re: The 22 March 2014 build (9744) is out.
« Reply #62 on: May 08, 2014, 07:17:41 am »
I can confirm that the splashscreen is buggy under linux (mint 15) see some other posts...
Disablin the splashscreen avoids the bug... (but it won't fix it ;-) )

Offline carra

  • Multiple posting newcomer
  • *
  • Posts: 114
Re: The 22 March 2014 build (9744) is out.
« Reply #63 on: May 08, 2014, 09:50:55 am »
A minor bug I just came across: I was creating some custom variables in a project, and they contain spaces. I was prompted if I wanted to add quotes, so I checked "don't annoy me again" and clicked on "leave unquoted". However, the choice stored by C::B was "quote" and I have had to re-enable the dialog and click on it every time.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11267
    • Travis build status
Re: The 22 March 2014 build (9744) is out.
« Reply #64 on: May 09, 2014, 01:28:31 am »
@carra: Reproduced and fixed. Thank you for reporting.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

ToApolytoXaos

  • Guest
Re: The 22 March 2014 build (9744) is out.
« Reply #65 on: May 09, 2014, 03:35:00 pm »
PC Specs:
Windows 7 Enterprise 64-bit
TDM's GCC 4.8.1 32-bit
Code::Blocks svn9760


I think I have detected something that might be a bug.

Press Ctrl-J at any empty area of your choice: this works as expected


Press hash key and auto-completion works as expected:


Press ESC to close (interrupt) auto-completion suggestions and press again Ctrl-J: voila!


Is this behavior normal?

cheers.

P.S.: I have had a similar issue on my Debian PC with include guards adding randomly mixed characters as name before I even type it.

Offline Alpha

  • Developer
  • Lives here!
  • *****
  • Posts: 1513
Re: The 22 March 2014 build (9744) is out.
« Reply #66 on: May 09, 2014, 03:52:32 pm »
[...]
Code::Blocks svn9760
I think I have detected something that might be a bug. [...]
Abbreviations have stopped working correctly (at least under Windows) if trying to replace them when partially written. [...]
Oops, my fault.  I forgot to commit some local changes.  ... Unfortunately, the introduction of CCManager has further destabilized this feature of Abbreviations (which was already bugged, because it required event handling to be in a specific order, which it could not control).
[...]  I will try to deal with the event handling this weekend.
Okay, I guess I was somewhat later than expected.  Should be fixed in trunk now.
Rev. 9761 is the commit that should have addressed this.

Offline carra

  • Multiple posting newcomer
  • *
  • Posts: 114
Re: The 22 March 2014 build (9744) is out.
« Reply #67 on: May 09, 2014, 08:06:41 pm »
Thanks Obfuscated, that was quick!  :D

ToApolytoXaos

  • Guest
Re: The 22 March 2014 build (9744) is out.
« Reply #68 on: May 10, 2014, 11:46:59 am »
Rev. 9761 is the commit that should have addressed this.
I'm afraid it's not working. I just finished compiling the latest HEAD and the issue remains similarly the same.

First, I pressed Ctrl-J; it worked as expected.

Then by mistake I pressed \ character, then deleted it with backspace. I pressed hash key and then Ctrl-J and got this:


Offline Alpha

  • Developer
  • Lives here!
  • *****
  • Posts: 1513
Re: The 22 March 2014 build (9744) is out.
« Reply #69 on: May 10, 2014, 07:59:04 pm »
I'm afraid it's not working. I just finished compiling the latest HEAD and the issue remains similarly the same.
Hmm, are you certain the relevant components were actually (re)compiled and are being used (ran update)?

First, I pressed Ctrl-J; it worked as expected.
Then by mistake I pressed \ character, then deleted it with backspace. I pressed hash key and then Ctrl-J and got this: [...]
This looks even more odd, but I cannot seem to reproduce it (tried both Linux and Windows).  Is your local build completely vanilla?  Edit: never mind... just figured it out...
« Last Edit: May 10, 2014, 08:01:40 pm by Alpha »

Offline Alpha

  • Developer
  • Lives here!
  • *****
  • Posts: 1513
Re: The 22 March 2014 build (9744) is out.
« Reply #70 on: May 10, 2014, 08:27:01 pm »
I'm afraid it's not working. I just finished compiling the latest HEAD and the issue remains similarly the same.
Try it now.

ToApolytoXaos

  • Guest
Re: The 22 March 2014 build (9744) is out.
« Reply #71 on: May 10, 2014, 08:39:24 pm »
It seems OK now on my Debian PC. On Monday when I will go to work, I will test it as well.

Cheers @Alpha.