Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Crash on startup linux

(1/2) > >>

BlueHazzard:
hi,
i get regular crashes after startup if i change the focus from the splash screen to something else
C::B latest svn with wxWidgets 2.8.12
Linux Mint 15

backtrace from crash log:

--- Code: ---    <frame level="0"/>
    <frame level="1" function="wxAppBase::SendIdleEvents(wxWindow*, wxIdleEvent&amp;)" offset="0000007e"/>
    <frame level="2" function="wxAppBase::ProcessIdle()" offset="00000074"/>
    <frame level="3"/>
    <frame level="4" function="g_main_context_dispatch" offset="00000135"/>
    <frame level="5"/>
    <frame level="6" function="g_main_loop_run" offset="0000006a"/>
    <frame level="7" function="gtk_main" offset="000000a7"/>
    <frame level="8" function="wxEventLoop::Run()" offset="00000048"/>
    <frame level="9" function="wxAppBase::MainLoop()" offset="0000004c"/>
--- End code ---

the interesting is: if i use a command line argument like --verbose or --debug-log the crash didn't happen
if i disable the compiler and scripted wizard plugins the crash didn't happen. This two plugins are the only one who print something to the console...

has someone a idea or a hint?
greetings

oBFusCATed:
Does the crash happen if you start C::B under gdb?

BlueHazzard:
no, i can't reproduce it with gdb, because i 'm somehow not capable of getting any debug output to a console. I mean if i start gdb there is nowhere the output i see normally when i start c::b from the terminal. I think the bug is somewhere in the output code from the plugins... (probably not thread safe?)

greetings

oBFusCATed:
Why do you need to see the output?
There is no threading in the starup code (hope there isn't)!

BlueHazzard:

--- Quote from: oBFusCATed on March 18, 2014, 09:12:32 pm ---Why do you need to see the output?

--- End quote ---

if i didn't see the output the crash did not happen:


--- Quote from: BlueHazzard on March 18, 2014, 02:21:45 pm ---the interesting is: if i use a command line argument like --verbose or --debug-log the crash didn't happen

--- End quote ---

if i use this arguments, i doesn't see any output in the terminal, and so the crash doesn't happen...

i have reported this issue some time ago, and i was not the only one... http://forums.codeblocks.org/index.php/topic,18580.msg128796.html#msg128796
greetings

Navigation

[0] Message Index

[#] Next page