Author Topic: Release 15.12, RC1 has arrived  (Read 28421 times)

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9496
Re: Release 15.12, RC1 has arrived
« Reply #75 on: January 03, 2016, 10:39:50 am »
Deleting the %APPDATA%\Roaming\CodeBlocks folder should be enough to restore it to a default state.
Not necessarily - removing the whole folder would be correct. Or just follow the way I've told you.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9496
Re: Release 15.12, RC1 has arrived
« Reply #76 on: January 03, 2016, 10:41:33 am »
do you want me to upload my zipped %appdata%\CodeBlocks so you could examine it or should I just erase all my settings and start everything anew?
Probably a good thing... please do.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7265
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: Release 15.12, RC1 has arrived
« Reply #77 on: January 03, 2016, 10:57:36 am »
May I ask what creating an empty default.conf would cause? I mean, aren't all settings stored in the appdata?
It makes C::B portable and ensures that:
- its like plain new, after a fresh installation
- no other settings interfere with this version

-> I wanted to have a clean version.
And it keeps the old settings, if you remove the newly created files in the Code::Blocks folder.

Offline Grabusz

  • Multiple posting newcomer
  • *
  • Posts: 15
Re: Release 15.12, RC1 has arrived
« Reply #78 on: January 03, 2016, 11:12:13 am »
do you want me to upload my zipped %appdata%\CodeBlocks so you could examine it or should I just erase all my settings and start everything anew?
Probably a good thing... please do.

Assuming that you've meant the first option, here's a zip with the needed folder :D

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9496
Re: Release 15.12, RC1 has arrived
« Reply #79 on: January 03, 2016, 11:28:03 am »
Assuming that you've meant the first option, here's a zip with the needed folder :D
Works for me also with that config (having the compiler path adjusted, of course). What I don't have is exactly your compiler and the libs you've setup in the compiler options. So all I can say is that there is no issue with C::B and recent TDM GCC MinGW32/64.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline Grabusz

  • Multiple posting newcomer
  • *
  • Posts: 15
Re: Release 15.12, RC1 has arrived
« Reply #80 on: January 03, 2016, 11:42:59 am »
I think I'll just wait for 15.12 release and delete everything and set it up again (I've been thinking about this lately as I discovered that I have a "little" mess in files). So thanks for the time you spent trying to figure out what the problem is :)

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12020
    • Travis build status
Re: Release 15.12, RC1 has arrived
« Reply #81 on: January 03, 2016, 11:46:51 am »
15.12 (or 16.01) won't help you I think.

Can you run codeblocks inside gdb in a console and when it crashes post the output of the "bt" or "thread apply all bt" commands here?

@devs: Probably would be good idea to have a non-stripped or even debug builds for 15.12, so people code post proper backtraces. What do you think?
(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 MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9496
Re: Release 15.12, RC1 has arrived
« Reply #82 on: January 03, 2016, 11:58:25 am »
@devs: Probably would be good idea to have a non-stripped or even debug builds for 15.12, so people code post proper backtraces. What do you think?
I think I had mentioned that already: We can use the stripped version along with the original (unstripped) DLL's if provided by Lieven to get the symbols using the addr2line tool. (This will save us many bandwidth...) To make it easier to use - thats what the Addr2LineUI tool was designed for.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5226
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: Release 15.12, RC1 has arrived
« Reply #83 on: January 03, 2016, 02:19:42 pm »
@devs: Probably would be good idea to have a non-stripped or even debug builds for 15.12, so people code post proper backtraces. What do you think?
I think I had mentioned that already: We can use the stripped version along with the original (unstripped) DLL's if provided by Lieven to get the symbols using the addr2line tool. (This will save us many bandwidth...) To make it easier to use - thats what the Addr2LineUI tool was designed for.
Then, Killerbot still need to supply the "unstripped DLLs" somewhere, so that Addr2Lines tool can get the correct source file and line information.
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 Grabusz

  • Multiple posting newcomer
  • *
  • Posts: 15
Re: Release 15.12, RC1 has arrived
« Reply #84 on: January 04, 2016, 03:25:49 pm »
So... after unsuccessfully trying to compile gdb with msys I found a compiled version, run the C::B, successfully crashed it, attached it to gdb and used "thread apply all bt", here's the gdb output:

Code: [Select]
Attaching to process 5024
[New Thread 5024.0x3bc]
[New Thread 5024.0x1114]
[New Thread 5024.0x1084]
[New Thread 5024.0x1280]
[New Thread 5024.0x11b0]
[New Thread 5024.0x116c]
[New Thread 5024.0x1148]
[New Thread 5024.0x1150]
[New Thread 5024.0x1030]
[New Thread 5024.0xdc8]
[New Thread 5024.0x150c]
[New Thread 5024.0x1510]
[New Thread 5024.0x156c]
[New Thread 5024.0x15a8]
[New Thread 5024.0x15b4]
[New Thread 5024.0x15d0]
[New Thread 5024.0x15dc]
[New Thread 5024.0x1664]
Reading symbols from C:\Programy\CodeBlocks RC\codeblocks.exe...(no debugging symbols found)...done.
0x779e000d in ntdll!DbgBreakPoint () from C:\Windows\SysWOW64\ntdll.dll
(gdb) thread apply all bt

Thread 18 (Thread 5024.0x1664):
#0  0x779e000d in ntdll!DbgBreakPoint () from C:\Windows\SysWOW64\ntdll.dll
#1  0x77a6eede in ntdll!DbgUiRemoteBreakin () from C:\Windows\SysWOW64\ntdll.dll
#2  0x7afab70a in ?? ()
#3  0x00000000 in ?? ()

Thread 17 (Thread 5024.0x15dc):
#0  0x7579723b in USER32!GetPropW () from C:\Windows\syswow64\user32.dll
#1  0x7579cd81 in USER32!SendMessageW () from C:\Windows\syswow64\user32.dll
#2  0x6ccdb9b1 in wxExecuteThread(void*)@4 () from C:\Programy\CodeBlocks RC\wxmsw28u_gcc_cb.dll
#3  0x00002b10 in ?? ()
#4  0x00000000 in ?? ()

Thread 16 (Thread 5024.0x15d0):
#0  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#2  0x765614b9 in WaitForSingleObjectEx () from C:\Windows\syswow64\KernelBase.dll
#3  0x0000052c in ?? ()
#4  0x00000000 in ?? ()

Thread 15 (Thread 5024.0x15b4):
#0  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#2  0x765614b9 in WaitForSingleObjectEx () from C:\Windows\syswow64\KernelBase.dll
#3  0x0000051c in ?? ()
#4  0x00000000 in ?? ()

Thread 14 (Thread 5024.0x15a8):
#0  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#2  0x765614b9 in WaitForSingleObjectEx () from C:\Windows\syswow64\KernelBase.dll
#3  0x00000554 in ?? ()
#4  0x00000000 in ?? ()

Thread 13 (Thread 5024.0x156c):
#0  0x779f1f26 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779f1f26 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SysWOW64\ntdll.dll
#2  0x77a15d56 in ntdll!TpSetTimer () from C:\Windows\SysWOW64\ntdll.dll
#3  0x773433aa in KERNEL32!BaseThreadInitThunk () from C:\Windows\syswow64\kernel32.dll
#4  0x77a08fc2 in ntdll!RtlInitializeExceptionChain () from C:\Windows\SysWOW64\ntdll.dll
#5  0x77a08f95 in ntdll!RtlInitializeExceptionChain () from C:\Windows\SysWOW64\ntdll.dll
#6  0x00000000 in ?? ()

Thread 12 (Thread 5024.0x1510):
---Type <return> to continue, or q <return> to quit---
#0  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#2  0x765614b9 in WaitForSingleObjectEx () from C:\Windows\syswow64\KernelBase.dll
#3  0x0000048c in ?? ()
#4  0x00000000 in ?? ()

Thread 11 (Thread 5024.0x150c):
#0  0x779f013d in ntdll!ZwWaitForMultipleObjects () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779f013d in ntdll!ZwWaitForMultipleObjects () from C:\Windows\SysWOW64\ntdll.dll
#2  0x76561605 in WaitForMultipleObjectsEx () from C:\Windows\syswow64\KernelBase.dll
#3  0x00000002 in ?? ()
#4  0x0accfd34 in ?? ()
#5  0x77341a3c in WaitForMultipleObjectsEx () from C:\Windows\syswow64\kernel32.dll
#6  0x630e6402 in ?? () from C:\Programy\CodeBlocks RC\share\codeblocks\plugins\FileManager.dll
#7  0x6ccd8aec in wxThreadInternal::DoThreadStart(wxThread*) () from C:\Programy\CodeBlocks RC\wxmsw28u_gcc_cb.dll
#8  0x6ccd8be5 in wxThreadInternal::WinThreadStart(void*)@4 () from C:\Programy\CodeBlocks RC\wxmsw28u_gcc_cb.dll
#9  0x058c1ec0 in ?? ()
#10 0x761a1328 in msvcrt!_endthreadex () from C:\Windows\syswow64\msvcrt.dll
#11 0x773433aa in KERNEL32!BaseThreadInitThunk () from C:\Windows\syswow64\kernel32.dll
#12 0x77a08fc2 in ntdll!RtlInitializeExceptionChain () from C:\Windows\SysWOW64\ntdll.dll
#13 0x77a08f95 in ntdll!RtlInitializeExceptionChain () from C:\Windows\SysWOW64\ntdll.dll
#14 0x00000000 in ?? ()

Thread 10 (Thread 5024.0xdc8):
#0  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#2  0x765614b9 in WaitForSingleObjectEx () from C:\Windows\syswow64\KernelBase.dll
#3  0x00000200 in ?? ()
#4  0x00000000 in ?? ()

Thread 9 (Thread 5024.0x1030):
#0  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#2  0x765614b9 in WaitForSingleObjectEx () from C:\Windows\syswow64\KernelBase.dll
#3  0x00000294 in ?? ()
#4  0x00000000 in ?? ()

Thread 8 (Thread 5024.0x1150):
#0  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#2  0x765614b9 in WaitForSingleObjectEx () from C:\Windows\syswow64\KernelBase.dll
#3  0x000001e0 in ?? ()
#4  0x00000000 in ?? ()

Thread 7 (Thread 5024.0x1148):
---Type <return> to continue, or q <return> to quit---
#0  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#2  0x765614b9 in WaitForSingleObjectEx () from C:\Windows\syswow64\KernelBase.dll
#3  0x000001d8 in ?? ()
#4  0x00000000 in ?? ()

Thread 6 (Thread 5024.0x116c):
#0  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#2  0x765614b9 in WaitForSingleObjectEx () from C:\Windows\syswow64\KernelBase.dll
#3  0x000001d0 in ?? ()
#4  0x00000000 in ?? ()

Thread 5 (Thread 5024.0x11b0):
#0  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779ef8b1 in ntdll!ZwWaitForSingleObject () from C:\Windows\SysWOW64\ntdll.dll
#2  0x765614b9 in WaitForSingleObjectEx () from C:\Windows\syswow64\KernelBase.dll
#3  0x000001a4 in ?? ()
#4  0x00000001 in ?? ()
#5  0x038bff18 in ?? ()
#6  0x77341194 in WaitForSingleObjectEx () from C:\Windows\syswow64\kernel32.dll
#7  0x75b9cd63 in ole32!CoGetTreatAsClass () from C:\Windows\syswow64\ole32.dll
#8  0x75b9d86a in ole32!CoGetTreatAsClass () from C:\Windows\syswow64\ole32.dll
#9  0x773433aa in KERNEL32!BaseThreadInitThunk () from C:\Windows\syswow64\kernel32.dll
#10 0x77a08fc2 in ntdll!RtlInitializeExceptionChain () from C:\Windows\SysWOW64\ntdll.dll
#11 0x77a08f95 in ntdll!RtlInitializeExceptionChain () from C:\Windows\SysWOW64\ntdll.dll
#12 0x00000000 in ?? ()

Thread 4 (Thread 5024.0x1280):
#0  0x779f1f26 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779f1f26 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SysWOW64\ntdll.dll
#2  0x77a15d56 in ntdll!TpSetTimer () from C:\Windows\SysWOW64\ntdll.dll
#3  0x773433aa in KERNEL32!BaseThreadInitThunk () from C:\Windows\syswow64\kernel32.dll
#4  0x77a08fc2 in ntdll!RtlInitializeExceptionChain () from C:\Windows\SysWOW64\ntdll.dll
#5  0x77a08f95 in ntdll!RtlInitializeExceptionChain () from C:\Windows\SysWOW64\ntdll.dll
#6  0x00000000 in ?? ()

Thread 3 (Thread 5024.0x1084):
#0  0x779f1f26 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779f1f26 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\Windows\SysWOW64\ntdll.dll
#2  0x77a15d56 in ntdll!TpSetTimer () from C:\Windows\SysWOW64\ntdll.dll
#3  0x773433aa in KERNEL32!BaseThreadInitThunk () from C:\Windows\syswow64\kernel32.dll
#4  0x77a08fc2 in ntdll!RtlInitializeExceptionChain () from C:\Windows\SysWOW64\ntdll.dll
#5  0x77a08f95 in ntdll!RtlInitializeExceptionChain () from C:\Windows\SysWOW64\ntdll.dll
#6  0x00000000 in ?? ()
---Type <return> to continue, or q <return> to quit---

Thread 2 (Thread 5024.0x1114):
#0  0x779f013d in ntdll!ZwWaitForMultipleObjects () from C:\Windows\SysWOW64\ntdll.dll
#1  0x779f013d in ntdll!ZwWaitForMultipleObjects () from C:\Windows\SysWOW64\ntdll.dll
#2  0x77a15965 in ntdll!RtlDosPathNameToNtPathName_U () from C:\Windows\SysWOW64\ntdll.dll
#3  0x773433aa in KERNEL32!BaseThreadInitThunk () from C:\Windows\syswow64\kernel32.dll
#4  0x77a08fc2 in ntdll!RtlInitializeExceptionChain () from C:\Windows\SysWOW64\ntdll.dll
#5  0x77a08f95 in ntdll!RtlInitializeExceptionChain () from C:\Windows\SysWOW64\ntdll.dll
#6  0x00000000 in ?? ()

Thread 1 (Thread 5024.0x3bc):
#0  0x779f2262 in ntdll!RtlLeaveCriticalSection () from C:\Windows\SysWOW64\ntdll.dll
#1  0x6d14023a in pthread_spin_unlock () from C:\Programy\CodeBlocks RC\wxmsw28u_gcc_cb.dll
#2  0x00712da8 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5226
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: Release 15.12, RC1 has arrived
« Reply #85 on: January 04, 2016, 04:08:37 pm »
So... after unsuccessfully trying to compile gdb with msys I found a compiled version, run the C::B, successfully crashed it, attached it to gdb and used "thread apply all bt", here's the gdb output:
Thanks for the report. But there is not much information I see about the crash. Can you build C::B yourself? I think if you can, then the crash bt can have many source line information.

BTW: I reread your old posts, and I still not sure what exact steps you have to reproduce the crash.
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 ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5226
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: Release 15.12, RC1 has arrived
« Reply #86 on: January 04, 2016, 04:13:53 pm »
@Grabusz
I suggest write a bug report here Tickets
so that it won't lost, thanks.
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 oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12020
    • Travis build status
Re: Release 15.12, RC1 has arrived
« Reply #87 on: January 04, 2016, 08:08:56 pm »
(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 stahta01

  • Lives here!
  • ****
  • Posts: 6644
    • My Best Post
Re: Release 15.12, RC1 has arrived
« Reply #88 on: January 06, 2016, 04:16:47 am »
I was able to get CB GTK2 Wizard and MSys2 GCC Compiler to work with a very minor patch. CB Thread http://forums.codeblocks.org/index.php/topic,20827.msg142175.html#msg142175
The import library ends in .dll.a for the GTK2 file.

A user wanted GTK3 to work and I do NOT have the time to add the GUI front end to change between to two.
But, if the CB Devs can make this minor change before the next release it will be easy to write directions; so, an user can edit the current CB Wizard to use GTK3.

Thank you all for your hard work.

Tim S.

Code: [Select]
From b609f23f9b1f85b7375bac6ab985d35533bd13a0 Mon Sep 17 00:00:00 2001
From: Tim S <stahta01@users.sourceforge.net>
Date: Mon, 4 Jan 2016 19:09:16 -0500
Subject: [PATCH] * scriptedwizard: Added option to look for "libGL.dll.a" if
 all else fails.(Thanks stahta01)

---
 src/plugins/scriptedwizard/resources/common_functions.script | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/plugins/scriptedwizard/resources/common_functions.script b/src/plugins/scriptedwizard/resources/common_functions.script
index f9691a1..15d8537 100644
--- a/src/plugins/scriptedwizard/resources/common_functions.script
+++ b/src/plugins/scriptedwizard/resources/common_functions.script
@@ -551,7 +551,8 @@ function SilentVerifyLibFile(dir, file)
             || IO.FileExists(dir + wxFILE_SEP_PATH + _T("lib") + file + _T(".a"))
             || IO.FileExists(dir + wxFILE_SEP_PATH + _T("lib") + file + _T(".lib"))
             || IO.FileExists(dir + wxFILE_SEP_PATH + _T("lib") + file + _T(".la"))
-            || IO.FileExists(dir + wxFILE_SEP_PATH + _T("lib") + file + _T(".so")) );
+            || IO.FileExists(dir + wxFILE_SEP_PATH + _T("lib") + file + _T(".so"))
+            || IO.FileExists(dir + wxFILE_SEP_PATH + _T("lib") + file + _T(".dll") + _T(".a")) );
 }
 
 // verify the existence of a file of library type (add prefix lib, postfix .a and .lib)
--
2.7.0.windows.1
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9496
Re: Release 15.12, RC1 has arrived
« Reply #89 on: January 06, 2016, 07:40:11 am »
But, if the CB Devs can make this minor change before the next release it will be easy to write directions; so, an user can edit the current CB Wizard to use GTK3.
Done that in SVN (slightly modified).
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ