Crash report

[Aural Architect]

Ukelele has crashed several times under the same circumstances.  It happens with sticky modifier keys on and changing modifiers.  It seems to only happen when removing modifier keys, not when adding them...

Here is a copy of the corresponding crash report:

Process:         Ukelele [296]
Path:            /Applications/Ukelele.app/Contents/MacOS/Ukelele
Identifier:      org.sil.Ukelele
Version:         3.2.5 (3.2.5.180)
Code Type:       X86-64 (Native)
Parent Process:  launchd [256]
User ID:         501

Date/Time:       2017-05-17 02:08:29.615 -0400
OS Version:      Mac OS X 10.8.5 (12F2560)
Report Version:  10

Interval Since Last Report:          45775070 sec
Crashes Since Last Report:           91216
Per-App Interval Since Last Report:  166114 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      F1085229-5C34-2C25-1BDA-04D3DF94F969

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000000e0

VM Regions Near 0xe0:
-->
    __TEXT                 0000000103e7c000-0000000104096000 [ 2152K] r-x/rwx SM=COW  /Applications/Ukelele.app/Contents/MacOS/Ukelele

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.sil.Ukelele                   0x0000000103f318a8 KeyMapElement::GetKeyElement(unsigned int) const + 0
1   org.sil.Ukelele                   0x0000000103edd68f KeyboardElement::GetCharOutput(unsigned int, unsigned int, unsigned int, NString, bool&, NString&) const + 81
2   org.sil.Ukelele                   0x0000000103ea296e -[UkeleleKeyboardObject getCharOutput:isDead:nextState:] + 440
3   org.sil.Ukelele                   0x0000000103f3defd -[UKKeyboardController updateUkeleleView:state:modifiers:usingFallback:] + 1248
4   org.sil.Ukelele                   0x0000000103f3d95e -[UKKeyboardController updateWindow] + 203
5   org.sil.Ukelele                   0x0000000103f45e20 -[UKKeyboardController messageClick:] + 824
6   org.sil.Ukelele                   0x0000000103f45297 -[UKKeyboardController handleKeyCapClick:clickCount:] + 101
7   org.sil.Ukelele                   0x0000000103f52a47 -[KeyCapView mouseDown:] + 132
8   com.apple.AppKit                  0x0000000104e1b50e -[NSWindow sendEvent:] + 6853
9   com.apple.AppKit                  0x0000000104e17644 -[NSApplication sendEvent:] + 5761
10  com.apple.AppKit                  0x0000000104d2d21a -[NSApplication run] + 636
11  com.apple.AppKit                  0x0000000104cd1bd6 NSApplicationMain + 869
12  libdyld.dylib                     0x00000001077887e1 start + 1

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib            0x0000000107966d16 kevent + 10
1   libdispatch.dylib                 0x0000000107758dea _dispatch_mgr_invoke + 883
2   libdispatch.dylib                 0x00000001077589ee _dispatch_mgr_thread + 54

Thread 2:: OGL Profiler
0   libsystem_kernel.dylib            0x0000000107964686 mach_msg_trap + 10
1   libsystem_kernel.dylib            0x0000000107963c42 mach_msg + 70
2   com.apple.opengl                  0x0000000108e01a9d glcDebugListener + 405
3   libsystem_c.dylib                 0x00000001077ed772 _pthread_start + 327
4   libsystem_c.dylib                 0x00000001077da1a1 thread_start + 13

Thread 3:: CVDisplayLink
0   libsystem_kernel.dylib            0x00000001079660fa __psynch_cvwait + 10
1   libsystem_c.dylib                 0x00000001077f1fb9 _pthread_cond_wait + 869
2   com.apple.CoreVideo               0x00000001112772a1 CVDisplayLink::runIOThread() + 689
3   com.apple.CoreVideo               0x0000000111276fd7 startIOThread(void*) + 148
4   libsystem_c.dylib                 0x00000001077ed772 _pthread_start + 327
5   libsystem_c.dylib                 0x00000001077da1a1 thread_start + 13

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x00007ffa49e9dd40  rcx: 0x0000000000000008  rdx: 0x0000000000000000
  rdi: 0x0000000000000000  rsi: 0x0000000000000035  rbp: 0x00007fff5bd82770  rsp: 0x00007fff5bd82508
   r8: 0x0000000000000001   r9: 0x0000000066605d3f  r10: 0x00007ffa4ee4ad80  r11: 0x0000000028c3cae2
  r12: 0x0000000000000001  r13: 0x0000000000000035  r14: 0x0000000000000a00  r15: 0x0000000000000000
  rip: 0x0000000103f318a8  rfl: 0x0000000000010293  cr2: 0x00000000000000e0
Logical CPU: 6



Hope that helps, let me know if any additional information is needed or would be helpful.

[Aural Architect]

SOLVED - false alarm...  (it seems...)

I was troubleshooting the problem and I found that I could not duplicate the issue with other keylayouts.  So I took a closer look at the file and found an error- or rather an omission.
I had added a new modifier layer, telling Ukelele to duplicate the currently selected layer.  Apparently a new map index was created by the corresponding keyMap was not created and the crash was occurring whenever I tried to switch to that layer.
I manually copied and pasted the keyMap and adjusted the index number and now the problem seems to be solved.

The strange thing is that I created two new layers (copying two existing keyMaps) and the first one completed successfully/correctly, but the second time the keyMap was not duplicated.  I didn't discover the error until several days/sessions later when I finished modifying the first one.  Up to that point that I tried to switch to that layer there were no issues.

[Gé van Gasteren]

Jon, you did all that in the XML code, or within Ukelele?

--
You received this message because you are subscribed to the Google Groups "Ukelele Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukelele-users+unsubscribe@googlegroups.com.
To post to this group, send email to ukelel...@googlegroups.com.
Visit this group at https://groups.google.com/group/ukelele-users.
For more options, visit https://groups.google.com/d/optout.

[Aural Architect]

I performed the XML edits with either TextWrangler or Sublime— I don't recall which, I use them both frequently, probably Sublime as it has more features & plugins for working with XML.  It's kind of tedious work, but I don't believe there's any way to do all that within Ukelele.

(Sorry about such a delayed response!)

To unsubscribe from this group and stop receiving emails from it, send an email to ukelele-user...@googlegroups.com.

[Gé van Gasteren]

Hi Aural Architect/Jon,

John Brownie is kind enough to look at any keyboard-layout-problems you throw at him, but in principle, such questions are not relevant on a Ukelele forum, don’t you think?

Maybe it took you so long to respond this time because you realized you had forgotten to mention in your first post that the editing was done manually? We’re all human…

[Aural Architect]

I understand your reasoning & appreciate your concern.  Actually, John asked me to post reports of any crashes of Ukelele...   That was my reason for posting, I wasn't doing it to get support.

I didn't mention that I had edited the files manually in my first post because I had not yet determined what was causing the crash.  And at this point I believe that ALL of my .keylayout files have probably been edited manually at some point (John has been kind enough to give me some pointers to help me troubleshoot issues on my own by checking the XML).

Yes, indeed!  We are human, and I'm well aware that I can be fairly prone to err.  I am quick and not embarrassed or shy to own up to that promptly!  :)

There were actually a couple of reasons for my delayed response.  The main one being that I didn't expect any follow-up or response because my second post was to basically "close" the issue and explain what happened, how I resolved it and that it WAS my fault to begin with- so why check back?  I've also been out of state for family emergencies & events, and as a serious gardener this is quite a busy time of year for me  :)

Cheers!

[Gé van Gasteren]

All right, I think we’re on the same wavelength again :)

It’s true, John of course wants Ukelele to be as robust as possible, which includes "failing gracefully" when XML files contain errors and cause trouble.

In fact, a few versions ago, I was fiddling with modifier sets without understanding what I was doing (I still don’t, but that’s another chapter) and if I remember correctly, I had defined two sets which overlapped somehow, and that made Ukelele crash repeatedly, until I managed to get them sorted out properly. So even without touching XML, this area seems to be a bit fragile.

I didn’t know there were special editors for XML code, thanks for those. I may want to have a look myself at some point...

--
You received this message because you are subscribed to the Google Groups "Ukelele Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ukelele-users+unsubscribe@googlegroups.com.