Author Topic: The 01 october 2006 build is out.  (Read 13881 times)

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2143
Re: The 01 october 2006 build is out.
« Reply #15 on: October 03, 2006, 02:13:42 pm »
Hello all,
I experience some troubles for quite some time now regarding windows shutdown and codeblocks crash. When I shutdown my computer and codeblocks is still running, codeblocks always crash even when you are prompted to save your work. Saving works but codeblocks crashes afterwards. No problem closing codeblocks normally (not forced by a windows shutdown)
Any ideas?
Jan

I can confirm that on Windows XPsp2, shutting down with CB open (SVN 3001 and prior) causes CB to crash and hangs the shutdown.

I'll see if I can get a backtrace on this.
« Last Edit: October 03, 2006, 02:22:49 pm by Pecan »

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2143
Re: The 01 october 2006 build is out.
« Reply #16 on: October 03, 2006, 07:29:11 pm »
Hello all,
I experience some troubles for quite some time now regarding windows shutdown and codeblocks crash. When I shutdown my computer and codeblocks is still running, codeblocks always crash even when you are prompted to save your work. Saving works but codeblocks crashes afterwards. No problem closing codeblocks normally (not forced by a windows shutdown)
Any ideas?
Jan

I can confirm that on Windows XPsp2, shutting down with CB open (SVN 3001 and prior) causes CB to crash and hangs the shutdown.

I'll see if I can get a backtrace on this.


Looks like I'm not going to get a backtrace on this one. It shuts down just fine when run under GDB. But still crashes on shutdown otherwise.

Does that "woah" window produce a backtrace? I dont seem to find one anywhere.
« Last Edit: October 05, 2006, 07:09:40 pm by Pecan »

Offline sque

  • Multiple posting newcomer
  • *
  • Posts: 65
Re: The 01 october 2006 build is out.
« Reply #17 on: October 05, 2006, 05:06:46 pm »
There is another CC problem with macros.

I have declared a macro at header let's say testa.h:
Code: C++
  1. #define SLIB_DECLARE_EXCEPTION(name, type) \   // << A there is a bug at forums C++ format plugin too :P
  2.     class name : public Exception { \
  3.     public : name (int error, const string desc, const string func, const string file, long line) \
  4.     : Exception(error, desc, func, file, line, type) {} }; \

At another file
Code: C++
  1. #include "testa.h"
  2.  
  3. // MyException1 declared with normal way
  4. class MyException1 : public Exception
  5. {
  6. public :
  7.     MyException1(int error, const string desc, const string func, const string file, long line)
  8.        :  Exception(error, desc, func, file, line, "MyException1")
  9.      {}
  10. };
  11.  
  12. // MyException2 Declared using my macro
  13. SLIB_DECLARE_EXCEPTION(MyException2, "MyException2");
  14.  
  15. // <<< Here code completition sees only MyException1
  16.  

Is it possible to be implemented, or it is too complicated?
« Last Edit: October 05, 2006, 05:09:59 pm by sque »
Tell me a bug and I 'll tell you two  :twisted:

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Re: The 01 october 2006 build is out.
« Reply #18 on: October 05, 2006, 05:21:56 pm »
Quote
Is it possible to be implemented, or it is too complicated?

Nope it won't be implemented because it's too complicated. As a matter of fact we would need to actually evaluate preprocessor macros which won't ever happen ;).
Be patient!
This bug will be fixed soon...