Author Topic: The 06 December 2014 build (10050) is out.  (Read 25179 times)

Offline eMan.Lived

  • Multiple posting newcomer
  • *
  • Posts: 21
Re: The 06 December 2014 build (10050) is out.
« Reply #30 on: January 12, 2015, 03:06:04 pm »
Project B is also present.
[AAAA|+}

Offline scarphin

  • Lives here!
  • ****
  • Posts: 644
Re: The 06 December 2014 build (10050) is out.
« Reply #31 on: January 13, 2015, 03:46:16 pm »
I realized 'clear' button in 'project build options -> search directories -> compiler|linker|resource compiler' doesn't work if nothing is selected. Can anyone else reproduce this?

Win7 x64

Offline Melchior

  • Multiple posting newcomer
  • *
  • Posts: 64
  • Sage of Life, Reason, and Time
Re: The 06 December 2014 build (10050) is out.
« Reply #32 on: January 14, 2015, 12:33:07 am »
i got around this by editing the
Project build options --> Custom variables -->
changing  [WX_SUFFIX = u]  to [WX_SUFFIX = ud] for each and every file
Yes, the workspace don't have compiler settings, so you need to change the cbp files. Besides the WX_SUFFIX change, you may also need an extra -D__WXDEBUG__ for every cbp, see: annoying crash when debugging CC's auto-suggestion. For git(I use git-svn), this is not an issue, because you can have many branches, and synchronize with our SVN head.


yah that looks like what I was probably missing... thx Olly
-D__WXDEBUG__
but this I should be able to add that to the CodeBlocks Global variable base  along with -g..

so this is what it will look like for me ("" are used only to indicate string)
"F:\Dev-src\CodeBlocks_src -g -D__WXDEBUG__"


_______________________
EDIT



I cleaned out the old rpt file and  and tried  loading  "Notepad2.vcproj"
using the custom File Type Associations I had created
(I will get to trying to compile that Debug build later...)
Code: [Select]
-------------------

Error occurred on Tuesday, January 13, 2015 at 20:43:53.

C:\Dev-CodeBlocks\codeblocks.exe caused an Access Violation at location 6d053d40 in module
C:\Dev-CodeBlocks\wxmsw28u_gcc_cb.dll
Reading from location 00000000.

Registers:
eax=0000000d  ebx=084e7fd4  ecx=00000000  edx=00000001  esi=00000001  edi=0000000d
eip=6d053d40   esp=007bf2c8  ebp=00000000  iopl=0         nv up ei pl nz na pe nc
cs=0023              ss=002b            ds=002b            es=002b 
fs=0053              gs=002b            efl=00010202

Call stack:


DrWatson Log excerpt:
Code: [Select]
        Exception number: c0000005 (access violation)

the Fault -> area stripped w/ no usable data!

Loi... 
C:\Dev-CodeBlocks\codeblocks.exe   caused an Access Violation
at location 6d053d40
in module
C:\Dev-CodeBlocks\wxmsw28u_gcc_cb.dll     <<-- PERHAPS THAT IS WHY I NEEDED to BUILD WxWidgets  as Debug!!  ;) 8)
« Last Edit: January 14, 2015, 03:04:35 am by Melchior »
(PC Specs)
CPU: AMD FX-9590 4.7GHz 8-core  RAM: 32GB
Motherboard: Asus SABERTOOTH 990FX R2.0
GPU: nVidia GTX 1070 Ti 8GB  --  GFX Drivers: Nvidia v431.60
OS: Windows 7 Ultimate 64-bit SP1 (x64)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5241
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: The 06 December 2014 build (10050) is out.
« Reply #33 on: January 14, 2015, 03:47:05 am »
...
so this is what it will look like for me ("" are used only to indicate string)
"F:\Dev-src\CodeBlocks_src -g -D__WXDEBUG__"
...
Good catch, the "-D__WXDEBUG__" can be put in the global compiler variable.
What is the string "F:\Dev-src\CodeBlocks_src" used for? I think "-g -D__WXDEBUG__" should be enough.

Quote
_______________________
EDIT



I cleaned out the old rpt file and  and tried  loading  "Notepad2.vcproj"
using the custom File Type Associations I had created
(I will get to trying to compile that Debug build later...)
Code: [Select]
-------------------

Error occurred on Tuesday, January 13, 2015 at 20:43:53.

C:\Dev-CodeBlocks\codeblocks.exe caused an Access Violation at location 6d053d40 in module
C:\Dev-CodeBlocks\wxmsw28u_gcc_cb.dll
Reading from location 00000000.

Registers:
eax=0000000d  ebx=084e7fd4  ecx=00000000  edx=00000001  esi=00000001  edi=0000000d
eip=6d053d40   esp=007bf2c8  ebp=00000000  iopl=0         nv up ei pl nz na pe nc
cs=0023              ss=002b            ds=002b            es=002b 
fs=0053              gs=002b            efl=00010202

Call stack:


DrWatson Log excerpt:
Code: [Select]
        Exception number: c0000005 (access violation)

the Fault -> area stripped w/ no usable data!

Loi... 
C:\Dev-CodeBlocks\codeblocks.exe   caused an Access Violation
at location 6d053d40
in module
C:\Dev-CodeBlocks\wxmsw28u_gcc_cb.dll     <<-- PERHAPS THAT IS WHY I NEEDED to BUILD WxWidgets  as Debug!!  ;) 8)
I think you can simply start debugging C::B under C::B, and you can get a full call stack by GDB. Generally, the bug is in C::B source code.
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 Melchior

  • Multiple posting newcomer
  • *
  • Posts: 64
  • Sage of Life, Reason, and Time
Re: The 06 December 2014 build (10050) is out.
« Reply #34 on: January 14, 2015, 07:01:45 am »
When opening Code::Blocks Project files or workspace files... 
CodeBlocks notifies me that there are THREE global variables that are part of  CB's src

THAT MUST BE DEFINED and cannot be left [void].....
"The base member is mandatory!"

the are as follows:
Code: [Select]
boost:
base:"F:\Dev-src\boost_1_57_0"


cb_release_type:
base: "F:\Dev-src\CodeBlocks_src -g -D__WXDEBUG__ "  <<-- The directory is the least thing I can put here... so it isn't null...
Lib : "F:\Dev-src\CodeBlocks_src\src\devel"          <<-- not fully sure what was needed so I added this one,
                                                                                                   CB doesn't complain....

wx:
Base   : "F:\Dev-src\wxMSW-2.8.12"                <<-- If more then the base is needed or not I am not sure...
Include: "F:\Dev-src\wxMSW-2.8.12\include"
Lib    : "F:\Dev-src\wxMSW-2.8.12\lib"
obj    : "F:\Dev-src\wxMSW-2.8.12\build\msw\gcc_mswuddll"
bin    : "F:\Dev-src\wxMSW-2.8.12\lib\gcc_dll"



"cb_release_type"
since this references a release build... shouldn't there be a "cb_debug_type"?
in which all debug global variables could be defined?

AND....  adding debug all target to take care of  the internal variables like
WX_SUFFIX = ud

File locations will vary, so it makes sense that  they would need to be defined this way as a global variable...
 ^_^ =D

instead of forcing everyone to jump through hoops to get release/debug setup why not added

targets: all_release, all_debug

and instead adding " -g -D__WXDEBUG__ " to the global variable base... they should be added in here as part a a debug target:
Code: [Select]
$(#CB_RELEASE_TYPE)
-pipe
-mthreads
-fmessage-length=0
-fexceptions
-Winvalid-pch
-g
-D__WXDEBUG__


I think you can simply start debugging C::B under C::B, and you can get a full call stack by GDB. Generally, the bug is in C::B source code.
... maybe once I am finished compiling it.. right?




__________________
EDIT4:


-g
-D__WXDEBUG__

with these added to the global variable cb_release_type's base..  that only leaves...
WX_SUFFIX = ud
and finding a way to get it overwrite the cb project files default value *without* modifying the cbp files




for that other mention of using git, git doesn't run on XP anymore... it will not install...



____________________
EDIT5:

attachment
« Last Edit: January 14, 2015, 07:40:38 am by Melchior »
(PC Specs)
CPU: AMD FX-9590 4.7GHz 8-core  RAM: 32GB
Motherboard: Asus SABERTOOTH 990FX R2.0
GPU: nVidia GTX 1070 Ti 8GB  --  GFX Drivers: Nvidia v431.60
OS: Windows 7 Ultimate 64-bit SP1 (x64)

Offline Melchior

  • Multiple posting newcomer
  • *
  • Posts: 64
  • Sage of Life, Reason, and Time
Re: The 06 December 2014 build (10050) is out.
« Reply #35 on: January 14, 2015, 11:04:55 am »
After a quite a bit of effort an tweaks to the project files and such
I got it finish compiling but its still crashing...  >:( >:(

some of the projects stored the "WX_SUFFIX = u" at the target level and did not get overwritten when I use the
Project Options Manipulator plugin to overwrite all the  u with ud
so I had to manually do it each time the compiler stopped to complain...

in contrib plugin  NassiShneiderman the way the project file was written needs help...
it targets  >:( long story short I had to do this for both base and include

Global Variable: boost
base   : "F:\Dev-src\boost_1_57_0\"
include: "F:\Dev-src\boost_1_57_0\"

Search.Dir.Compiler
$(#wx.include)           <<-- when  i set up wx I filled in all/most global variable, so this was safe  :P
$(#boost.include)      <<-- Really?!  ::)
$(#boost)                  <<-- is what it really should be because they declare the full path so only base is needed right?!
Code: [Select]
#include <boost/spirit/include/classic.hpp>
#include <boost/spirit/include/classic_core.hpp>
#include <boost/spirit/include/classic_symbols.hpp>
#include <boost/spirit/include/classic_confix.hpp>



___________________
EDIT1:

I found adplus in the Debbuging tools for windows I had installed a while back.... so I gave it a try
archive with logs attached,

dmp files are way to big..
140MB - FULLDUMP_FirstChance_epr_Process_Shut_Down_codeblocks.exe__04d4_2015-01-14_18-54-24-593_03a4.dmp
140MB - FULLDUMP_SecondChance_av_AccessViolation_codeblocks.exe__04d4_2015-01-14_18-54-19-859_03a4.dmp
8.5MB  - MINIDUMP_FirstChance_av_AccessViolation_codeblocks.exe__04d4_2015-01-14_18-54-11-812_03a4.dmp
« Last Edit: January 15, 2015, 01:04:30 am by Melchior »
(PC Specs)
CPU: AMD FX-9590 4.7GHz 8-core  RAM: 32GB
Motherboard: Asus SABERTOOTH 990FX R2.0
GPU: nVidia GTX 1070 Ti 8GB  --  GFX Drivers: Nvidia v431.60
OS: Windows 7 Ultimate 64-bit SP1 (x64)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5241
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: The 06 December 2014 build (10050) is out.
« Reply #36 on: January 18, 2015, 08:17:00 am »
@Melchior

Quote
"cb_release_type"
since this references a release build... shouldn't there be a "cb_debug_type"?
in which all debug global variables could be defined?
"release_type" does not mean this is a "release build", the value of "cb_release_type" can be either "release version" or "debug version". For the "debug version", you need "-g", and for "release version", you may need "-O2"

Quote
cb_release_type:
base: "F:\Dev-src\CodeBlocks_src -g -D__WXDEBUG__ "  <<-- The directory is the least thing I can put here... so it isn't null...
Lib : "F:\Dev-src\CodeBlocks_src\src\devel"          <<-- not fully sure what was needed so I added this one,
                                                                                                   CB doesn't complain....
I think you don't need to set the "lib" field, only "base" field is enough. It is the same to the wx global compiler variable.

Quote
...
instead adding " -g -D__WXDEBUG__ " to the global variable base... they should be added in here as part a a debug target:
...
Yes, the "-D__WXDEBUG__" can be put there if you want to build C::B against debug version of wx library.

Quote
for that other mention of using git, git doesn't run on XP anymore... it will not install...
Use msysgit, it works fine in my Windows XP.

Quote
some of the projects stored the "WX_SUFFIX = u" at the target level and did not get overwritten when I use the
Project Options Manipulator plugin to overwrite all the  u with ud
so I had to manually do it each time the compiler stopped to complain...
I never used project Options Manipulator plugin, cbp files are just XML files, so you can just open those files in any editor, and search and replace those text from "WX_SUFFIX = u" to "WX_SUFFIX = ud".

BTW: I suggest you to use GDB to get the useful crash report and call stack. You don't need to build C::B against debug version of wx, I think building C::B against release of wx is enough to catch the crash. I don't use other debugging tools, so I don't understand you posted logs from other tools.

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: 12090
    • Travis build status
Re: The 06 December 2014 build (10050) is out.
« Reply #37 on: January 24, 2015, 04:47:55 pm »
I realized 'clear' button in 'project build options -> search directories -> compiler|linker|resource compiler' doesn't work if nothing is selected. Can anyone else reproduce this?
Yes, I'm able to reproduce it and I have a fix for it in my local repo...
(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 scarphin

  • Lives here!
  • ****
  • Posts: 644
Re: The 06 December 2014 build (10050) is out.
« Reply #38 on: January 25, 2015, 12:33:21 am »
Nice to hear that.