Menu ▾ ▴

#230 build Abort button hangs in wx2.8 (wx3.0 is ok)

Undefined
wont-fix
bluehazzard
Compiler (40)
Undefined
2021-12-18
2015-10-02
gabyx
No

the build abort button and menu command, is slow, meaning, when the abort command is issued it takes ages that the compiler is shutdown and "Build failed" is shown, this is annoying.
It actually waits till the compiler is finished instead of killing it? Is that general behavior
in wx3.0 (the abort button experience is different, it instantly kills the process and instead of waiting till the process is killed. (in wx2.8) -> manually killing compiler in terminal helps to avoid the long wait of codeblocks...

May be this me having wrong settings, but can the abort button be made in wx2.8 that it instantly kills the compiler.

Somebody already experienced this?

Discussion

  • gabyx

    gabyx - 2015-10-02

    it has to be said that I build cmake generated projects...

     

  • gabyx

    gabyx - 2015-10-02

    killall c++ make cmake cc1plus
    in the terminal
    solves the issue

     

    Last edit: gabyx 2015-10-02

  • gabyx

    gabyx - 2015-10-02

    Corrections:
    May be this me having wrong settings, but can the abort button be made in wx2.8 that it instantly kills the compiler.

     

  • ollydbg

    ollydbg - 2015-10-06
    • labels: --> Compiler
     

  • ollydbg

    ollydbg - 2015-10-06

    If I remember correctly, in the dev internal forum, thomas has suggest to use a kill command to stop the compiler process, not the normal way.

     

  • ollydbg

    ollydbg - 2015-10-06
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -2,7 +2,7 @@
 It actually waits till the compiler is finished instead of killing it? Is that general behavior
 in wx3.0 (the abort button experience is different, it instantly kills the process and instead of waiting till the process is killed. (in wx2.8) -> manually killing compiler in terminal helps to avoid the long wait of codeblocks...

-May be this me having wrong settings, but can the abort button be made in wx2.8 that it instantly kills the debugger.
+May be this me having wrong settings, but can the abort button be made in wx2.8 that it instantly kills the compiler.

 Somebody already experienced this?
     

  • bluehazzard

    bluehazzard - 2019-01-20
    • assigned_to: bluehazzard
     

  • bluehazzard

    bluehazzard - 2019-01-20

    is this bug still relevant?
    There were changes for aborting the build process and i think they fixed this bug. Can you confirm by testing with the latest nightly?

     

    • Teodor Petrov

      Teodor Petrov - 2019-01-21

      Yes, I see this bug when ninja-build is building on all threads of the cpu... C::B isn't capable of killing it. I've not debugged why it happens, yet. Also, I'm not sure it happens with wx3.x, because I'm using wx2.8 on my work machine.

       

  • Miguel Gimenez

    Miguel Gimenez - 2021-12-18
    • status: open --> wont-fix
     

  • Miguel Gimenez

    Miguel Gimenez - 2021-12-18

    wx2.8 support has been removed

     

Log in to post a comment.