Re: [Qemu-devel] [PATCH] Mac OS X: QEMU crashes when pressing dead keys

[Mike Kronenberg]

On 08.12.2005, at 18:21, Joachim Henke wrote:

> This concerns the current cocoa version in cvs:  When typing into the
> monitor and accidentally pressing a dead key, qemu quits  
> immediately and
> all unsafed data in the guest os is lost:
>
> 2005-12-04 15:15:00.833 qemu[193] Exception raised during posting  
> of notification.  Ignored.  exception: *** -[NSCFString  
> characterAtIndex:]: Range or index out of bounds
>
> Even if you don't have a Mac, you can retrace this bug by following  
> these
> links:
>
> http://developer.apple.com/documentation/Cocoa/Reference/ 
> ApplicationKit/ObjC_classic/Classes/NSEvent.html#//apple_ref/occ/ 
> instm/NSEvent/characters
> http://developer.apple.com/documentation/Cocoa/Reference/Foundation/ 
> ObjC_classic/Classes/NSString.html#//apple_ref/occ/instm/NSString/ 
> characterAtIndex:
>
> [event characters] returns an empty string for dead keys, and so  
> calling
> [[event characters] characterAtIndex:0] will raise an  
> NSRangeException that
> crashes qemu. The following patch fixes this bug:


> To Mike Kronenberg: Q has the same problem. Pressing a dead key in the
> monitor locks the emulation and you're not able to do anything  
> further.
> Would you be so kind to confirm this? It seems that Fabrice doesn't  
> trust
> my fixes. Thanks!
>
> Regards
>         Jo.

Thanks for this correction,

it does indeed fix the dead key issue which I was not aware of, when  
I wrote that code to retrieve isochars. (I have no dead keys on my PB  
Keyboard :) )

Fixed this in Q. But the next Build will have to wait a little, since  
we have some other Problems on OS X.
Maybe You can help us out a little with this:

When running DOS/DOS Prompt under windows under QEMU, I experience  
crashes all the way.
With freedos I have figured out, that loading himem or xms will crash  
QEMU (Option 1). Option 3 (no Drivers) works. So it could be a memory  
mapping issue... DOOM crashes half way down.

This behaviour was introduced with the new MP Code. It's not related  
to cocoa.m, it also happens with SDL. I have the same Result with  
Tiger and Panther. There are no public builds yet... that would  
generate to much mails :)

Maybe You could just reproduce this issue?

Mike