Strange crash, can anyone give some pointers?

Targets macOS
1

I’ve got a customer who can’t run my application and the crash report is perplexing at most!

[quote]Process: bash [1156]
Path: /usr/local/Cellar/bash/4.3.11/bin/bash
Identifier: bash
Version: ???
Code Type: X86-64 (Native)
Parent Process: Document Icon Maker [1151]
Responsible: Document Icon Maker [1151]
User ID: 501

Date/Time: 2014-05-30 02:30:06.449 -0400
OS Version: Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: 49BDBCA7-56F9-0907-F483-0E031C98AD90

Crashed Thread: 0

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
Library not loaded: /usr/local/opt/readline/lib/libreadline.6.dylib
Referenced from: /usr/local/bin/bash
Reason: no suitable image found. Did find:
/usr/local/opt/readline/lib/libreadline.6.dylib: open() failed with errno=1

Binary Images:
0x7fff6015f000 - 0x7fff60192817 dyld (239.4) <042C4CED-6FB2-3B1C-948B-CAF2EE3B9F7A> /usr/lib/dyld[/quote]

Can anyone smarter than me, decrypt this and give me a clue please. All I can figure is that my Xojo built application is calling bash at some point.

2

I doubt I’m smarter than you but it seems like this user happens to have part of the ReadLine library missing, causing Bash to complain when your app uses a shell. Your user could reinstall ReadLine using MacPorts or Homebrew which seems likely to fix this.

3

[quote=93777:@Sam Rowlands]I’ve got a customer who can’t run my application and the crash report is perplexing at most!

Can anyone smarter than me, decrypt this and give me a clue please. All I can figure is that my Xojo built application is calling bash at some point.[/quote]

The user’s bash shell that they installed via homebrew is taking precedence over the system bash and is broken. When you create a shell, you should set its ‘Backend’ property to “/usr/bin/bash” to ensure that you get the system bash.

You should also file a bug report saying that Shell should default to an absolute path in order to avoid exactly this.

4

Thanks guys, I’ll look into updating my code and filing a feedback report.