#433 Running Code::Blocks causes shutdown error.

Undefined
open
nobody
None
Bug_Report
2016-11-17
2016-11-12
John Taylor
No

Running Code::Blocks on my Windows 10 computer causes a DDE Server Error on shutdown. It says memory at 0030 can't be written. I looked it up and that's a programmable interrupt controller. Is this problem on my end or yours?

Discussion

  • Teodor Petrov

    Teodor Petrov - 2016-11-12

    Is this error repeatable? Do you have a log, exact error message or something that could help us understand the problem?

    Which version do you use?

     
  • John Taylor

    John Taylor - 2016-11-12

    Error is definitely repeatable, I've tested it multiple times, and Code::Blocks is what triggers it. I use version 16.01. I can try to get the error message, but Windows finishes shutting down shortly after displaying it.

     
  • John Taylor

    John Taylor - 2016-11-12

    Wait, trying it out just now, went to grab a pencil and piece of paper before shutting down, and the error didn't repeat. Then I tried it again and it did. I think I know what's going on. I'm not giving Code::Blocks enough time to close before shutting down.

     
  • Teodor Petrov

    Teodor Petrov - 2016-11-13

    So you're saying that cb is causing your windows to restart, aren't you?

    If this is the case then this is not a cb problem, but some os or hardware related problem. If everything is fine with your os and hardware then a user program like cb won't be able to cause such havok on your system. We're not living in the windows 95/98 days anymore...

     
  • John Taylor

    John Taylor - 2016-11-13

    No, CB doesn't cause Windows to restart, it just causes an error when I do decide to shut down, but even then only if it's been less than half a minute between closing CB and shutting down. It's actually surprising that I was encountering the error as often as I was.

     
  • John Taylor

    John Taylor - 2016-11-13

    To be clear, by shutting down, I mean shutting down the OS. Shutting down Windows too quickly after closing CB causes an error message to briefly appear. Windows still shuts down fine though, so it's not that big a deal. Plus I can avoid it just by waiting 30 seconds between closing CB and shutting down.

     
  • John Taylor

    John Taylor - 2016-11-13

    I'd like to apologize if I'm being too direct. I do love the program.

     
  • John Taylor

    John Taylor - 2016-11-17

    Guess this mystery will go unsolved. :-/

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks