Opened 3 years ago
Last modified 19 months ago
#62945 new defect
abiword-x11 @3.0.4_1: crashes upon startup
Reported by: | cooljeanius (Eric Gallager) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.0 |
Keywords: | Cc: | mascguy (Christopher Nielsen) | |
Port: | abiword-x11 |
Description
I am on Big Sur with Xcode 12.5. When I start the abiword
binary provided by abiword-x11, it crashes. Starting it in a debugger gives this backtrace:
$ abiword Abort trap: 6 $ lldb abiword (lldb) target create "abiword" Current executable set to 'abiword' (x86_64). (lldb) break main invalid command 'breakpoint main'. (lldb) run Process 71545 launched: '/opt/local/bin/abiword' (x86_64) 2021-05-21 08:15:30.634980-0400 abiword[71545:41156713] SecTaskLoadEntitlements failed error=22 cs_flags=20, pid=71545 2021-05-21 08:15:30.635028-0400 abiword[71545:41156713] SecTaskCopyDebugDescription: abiword[71545]/0#-1 LF=0 Process 71545 stopped * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) frame #0: 0x00007fff206be898 CoreFoundation`CFArrayGetCount + 6 CoreFoundation`CFArrayGetCount: -> 0x7fff206be898 <+6>: movq (%rdi), %rax 0x7fff206be89b <+9>: testq %rax, %rax 0x7fff206be89e <+12>: je 0x7fff206be8bf ; <+45> 0x7fff206be8a0 <+14>: movq 0x5fca9ff1(%rip), %rcx ; __CFRuntimeClassTable + 8344 Target 0: (abiword) stopped. (lldb) bt * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) * frame #0: 0x00007fff206be898 CoreFoundation`CFArrayGetCount + 6 frame #1: 0x00000001037ec9fe libpangocairo-1.0.0.dylib`pango_core_text_family_list_faces + 373 frame #2: 0x00000001003b7b2b libabiword-3.0.dylib`GR_CairoGraphics::getAllFontNames() + 405 frame #3: 0x00000001003b7da7 libabiword-3.0.dylib`GR_CairoGraphics::getAllFontCount() + 9 frame #4: 0x0000000100278d1f libabiword-3.0.dylib`AP_UnixToolbar_FontCombo::AP_UnixToolbar_FontCombo(EV_Toolbar*, int) + 37 frame #5: 0x0000000100278cd2 libabiword-3.0.dylib`AP_UnixToolbar_FontCombo::static_constructor(EV_Toolbar*, int) + 34 frame #6: 0x00000001003d5202 libabiword-3.0.dylib`EV_UnixToolbar::synthesize() + 1620 frame #7: 0x00000001003a1922 libabiword-3.0.dylib`XAP_FrameImpl::_createToolbars() + 96 frame #8: 0x0000000100385cda libabiword-3.0.dylib`XAP_UnixFrameImpl::_createTopLevelWindow() + 1366 frame #9: 0x00000001002774ee libabiword-3.0.dylib`AP_UnixFrameImpl::_createWindow() + 14 frame #10: 0x0000000100275c40 libabiword-3.0.dylib`AP_UnixFrame::initialize(_FrameModes) + 142 frame #11: 0x000000010023f7c6 libabiword-3.0.dylib`AP_UnixApp::newFrame() + 42 frame #12: 0x000000010028ab0b libabiword-3.0.dylib`AP_App::openCmdLineFiles(AP_Args const*) + 269 frame #13: 0x0000000100240b5f libabiword-3.0.dylib`AP_UnixApp::main(char const*, int, char**) + 359 frame #14: 0x00007fff20641f3d libdyld.dylib`start + 1 (lldb) quit Quitting LLDB will kill one or more processes. Do you really want to proceed: [Y/n] y $ port installed abiword* The following ports are currently installed: abiword-x11 @3.0.4_1 (active) $ port provides /opt/local/bin/abiword /opt/local/bin/abiword is provided by: abiword-x11
Not sure if this is something I should report upstream, or if it's an issue with how MacPorts builds it...
Attachments (1)
Change History (8)
Changed 3 years ago by cooljeanius (Eric Gallager)
Attachment: | abiword_2021-05-21-081446_Eric-Gallagers-MacBook-Pro-2.crash added |
---|
comment:1 Changed 3 years ago by kencu (Ken)
what happens if you build it from source on this machine?
comment:2 Changed 3 years ago by cooljeanius (Eric Gallager)
I did build it from source; this is the abiword-x11 port that always builds from source, not the plain abiword port that has separate +use_binary
and +use_source
variants
comment:3 Changed 3 years ago by kencu (Ken)
well, that was my only hope for an easy fix for you :)
After that, it's running a debug build under lldb, enabling assertions if any, running the tests if any, looking at the warnings during the build for clues, running scan-build <https://clang-analyzer.llvm.org/scan-build.html> on it, seeing if upstream has already worked on it or fixed it, ...
This error can be tricky <https://code.tutsplus.com/tutorials/what-is-exc_bad_access-and-how-to-debug-it--cms-24544>
comment:4 Changed 3 years ago by kencu (Ken)
In this particular case maybe it could be easier; looks like it's trying to dereference 0x0
comment:5 Changed 19 months ago by mascguy (Christopher Nielsen)
Cc: | mascguy added |
---|
comment:6 Changed 19 months ago by mascguy (Christopher Nielsen)
Given that we've had multiple updates to pango
and cairo
over the past 18 months, I'm curious whether this crash still occurs?
comment:7 Changed 19 months ago by mascguy (Christopher Nielsen)
If the crash does still occur, you might want to do some Googling relative to libpangocairo
, specifically for a crash within pango_core_text_family_list_faces
. Along with checking the upstream project for pango
, to see if this is a known issue.
crash report for abiword