User forums > Nightly builds

The 19 July 2006 build is out.

<< < (3/4) > >>

dronT78:
Hello.

 I have a problem with C::B:
 My workspace contains several projects.
 Each project contains many build targets.
 All working great, but when i quit & C::B says "Workspace %s is modified. Do you want to save it?"
 i'm clicking Yes and after reopen workspace build targeds are not saved in from begin (top) in projects
 list to active project and saved from active project to end of projects list.
 Please fix this.
 My C::B build Jul 18 2006

Thanx (13 post)

killerbot:

--- Quote from: jpaterso on July 19, 2006, 03:39:53 pm ---It's crashing for me under Windows XP when I quit. If I try the 17th of July build --> no problem...

--- End quote ---

and then I wrote this becasue of this :

--- Quote ---# KeyBinder - v0.21 - Removed all dependencies on pushEventHander to avoid leaking handlers on unnotified window closuress
# Fixed multiple key profiles not being updated correctly when switching profiles without restarting CB
--- End quote ---


--- Quote from: killerbot on July 19, 2006, 04:36:54 pm ---could you try this , but with the keybinder plug-in disabled ??
do you have an rpt file ? if so what does it say ?

--- End quote ---


--- Quote from: JPlaroche on July 19, 2006, 08:09:25 pm ---open ide

compile my project    debug or release

ok

is quitte = scrash

os/winxp


--- End quote ---


@Pecan :
Since already 2 users started to have problems since the above mentioned changes, could it be it's purely because of this. They probably already redefined ctrl-Q (If they already done this in the first place?) and only now it seems to become a craashing problem ;-)

MortenMacFly:

--- Quote from: dronT78 on July 20, 2006, 08:42:57 am ---and after reopen workspace build targeds are not saved in from begin (top) in projects list to active project and saved from active project to end of projects list.

--- End quote ---
Sorry, I don't get what you are trying to explain. Could say that again with different words, maybe? What does not get saved? Or do you loose targets?!

Can you give a step-by-step description how to reproduce?

(Sorry, but I'm not a native english speaker.)

With regards, Morten.

Pecan:

--- Quote from: killerbot on July 20, 2006, 10:42:18 am ---
@Pecan :
Since already 2 users started to have problems since the above mentioned changes, could it be it's purely because of this. They probably already redefined ctrl-Q (If they already done this in the first place?) and only now it seems to become a craashing problem ;-)

--- End quote ---

The problem has been there since day one. There's a warning in the code by the original authors that Alt-F4 (his original quit key) caused crashes on termination.

I decided to delay doing anything about it in CodeBlocks until the situation proved his comments.

It's true, I changed the code to use Connect/Disconnect rather than PushEventHander. This was to avoid leaking event handlers when windows were closed without giving plugin notifications. Without notifications I had to leak the event handlers rather than crash the system.

I fixed the leaks. Then the original authors problem became my problem.
So I've temporarily  resorted to the same hack the original authors did. Namely, ignore *additional" key definitions to the quit menu item.

Note that you *can* redefine the quit menu key. But "additional" definitions other than the first will be ignored. The crash does not occur on the first key because the first of the three key definitions is  never seen by the keybinder event handler. Wx always traps its own menu key and dispatches it's own event handler.

What I don't understand yet, is why keybinder is being re-entered after it's been unloaded from memory. The reports on the forum would indicate that an errant branch from stack corruption is the culprit. This is just a guess. Ergo, a very low stack clobber is occuring somewhere in keybinder/widgets between the time keybinder gets the quit key and CB unloads and does a final return to widgets. Then widgets executes the clobbered stack, branching back into where keybinder "used" to be.

This is going to be hard to find. Thus I decided on the "ignore" hack to give me time to figure it out. I'd rather cripple the additional quit keys than leak the event handlers.

your thoughts?

regards,
pecan

killerbot:
thanks for the excellent info. I support your workaround. Hopefully we will be able to solve it completely, but till then we are now up and running without the crash ;-)

Navigation

[0] Message Index

[#] Next page

[*] Previous page