Hi all,
I found two workarounds for people who want to test or continue their work on the aqua native port.
The first solution is not to use native menus.
The secund is to comment a line in salframe.cxx (line 1680)
InstallAndRegisterEventHandler(NewEventHandlerUPP(HandleMenuPopulateEvent), 1, &cMenuPopulateEvent); Commenting this line makes menus empty (only the menu of the top), but OOo doesn't crash. Here's the result: http://lebasket.free.fr/OOo/05_02_07/OOom202.png This secund workaround shows us that the problem may come from HandleMenuPopulateEvent.

Ismael


Ismael a écrit :
Hi all,
I have finished my m202 build, and after some tests, i have some ideas about the causes of the crash. (I launched OOo with the terminal)
Without native menus, my OOo build didn't crash.
With native menus, I can resize the window without any problems, use the right click on the document, chose the police, the size and the style, click on some item of the tool bar. But once i make a window to be opened, or press a key, ooo crashes.
The common function on the stack is always:
1 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093 in secund position after another function which is very often but not always (i had another function that i can't get again now):
Thread 0 Crashed:
0 HandleMenuPopulateEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 216


At the top there always a stack like:
EXC_BAD_ACCESS (0x0001)
KERN_INVALID_ADDRESS (0x0001) at 0x6d656e7d

I use the m202 build without patches, language fr.

Ismael

Eric Hoch a écrit :
Hi all,
looks like me and at least James McKenzie have trouble with the latest Aqua OOo which persists of cws aquvcl01 based upon m202 out of SRC680 main code tree. Eric Bachard also reported crashs on IRC.
James get's the following error message:
AquaSalGraphics::drawAlphaBitmap not yet implemented!

I myself already had Pavel Janik and Eric Bachard take a look at a gdb output on IRC but otherwise I had no errors when starting the Aqua app. But starting the native OOo was close to everything I could do with this build. Both, James and Me, have Calc crashing or locking the whole OOo. In addition I can tell from my tryings that close to every action I want to try freezes OOo and I have to kill it via terminal. Only one out of five times at least able to navigate through the menu bar. With aquavcl based on older Milestones I barely had a crash. Also trying to start OOo using aquanative Menus fails here on my Mac Mini. This was also possible with earlier milestones. Eric B asked me to write this mail and ask others to provide their feedback with cws aquavcl01 based upon m202. While writing this mail a new build of aquavcl01 based upon m202 is running. I'll keep my fingers crossed that this time I'll have more luck and that the last time the frequent crashing were due to me/my build system applying bad coded patches.
Kind regards, Eric Hoch



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to