User forums > Nightly builds

The 22 March 2014 build (9744) is out.

<< < (11/15) > >>

nasty_wolverine:
when is the next nightly scheduled???
I tried this and the last nightly, both crash when attempting code completion. So, i went back to using the 13.12 release. I hear the crashes have been fixed in trunk, so patiently waiting for the next nightly.

ToApolytoXaos:
@jens: the latest nightly build from your repository on my Debian jessie 64-bit crashed a few seconds after i closed it and upon reopen the crash got reproduced.


--- Code: ---user@debian:~$ gdb codeblocks
GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
(gdb) bt
#0  0x00007ffff27589f8 in main_arena () from /lib/x86_64-linux-gnu/libc.so.6
#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.
0x00007ffff23ea3a9 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 0x7fffd7dc1700 (LWP 12975) exited]
[Thread 0x7fffd85c2700 (LWP 12946) exited]
[Thread 0x7fffe7309700 (LWP 12939) exited]
[Thread 0x7fffe7b0a700 (LWP 12938) exited]
[Thread 0x7fffe830b700 (LWP 12937) exited]

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb) continue
The program is not being run.
(gdb) q
user@debian:~$

--- End code ---

oBFusCATed:
try executing: "thread apply all bt" gdb command. The bt from the main trace doesn't look interesting or revealing...

Alpha:

--- Quote from: scarphin on April 26, 2014, 02:40:27 pm ---Good to know. Is it possible to provide a binary for Clang plugin somehow for volunteers like me to beta test? [...]

--- End quote ---
I will try to package a nightly build compatible Windows binary soon.


--- Quote from: vali29 on April 27, 2014, 09:58:30 am ---I have successfully compiled the ClangLib plugin but always crash at clang_getInclusions when they start to parse the project.

--- End quote ---
Odd...  Did you self-compile everything, or is this linking against a nightly?

vwdvaan:

--- Quote from: Alpha on May 01, 2014, 12:14:30 am ---

--- Quote from: vali29 on April 27, 2014, 09:58:30 am ---I have successfully compiled the ClangLib plugin but always crash at clang_getInclusions when they start to parse the project.

--- End quote ---
Odd...  Did you self-compile everything, or is this linking against a nightly?

--- End quote ---
Hi Alpha!

Compiled myself with TDM GCC 4.6.1, CB svn 9760, LLVM + Clang 3.3 and your ClangLib plugin.
On small CB projects, ex. c++ Hello World it's working but on projects with wxWidgets always crash.

Do you have a special build steps to compile LLVM with gcc on Windows?

Navigation

[0] Message Index

[#] Next page

[*] Previous page