App debugging on Catalina crashes with 19r1.1 and 19r2.1 with the same SEGFAULT

Targets macOS
1

I’m working to resolve an issue on Catalina with one of my projects and the project keeps crashing under the debugger on both 19r2.1 and 19r1.1. Here’s the Apple-generated backtrace from the crashes - it’s the same for both Xojo versions:

[code]Process: ArGest Backup 4.0.debug [952]
Path: /Volumes/VOLUME/*/ArGest Backup 4.0.debug.app/Contents/MacOS/ArGest Backup 4.0.debug
Identifier: com.tolisgroup.brupe
Version: 4.0.0 (4.0.0.3.235)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: ArGest Backup 4.0.debug [952]
User ID: 501

Date/Time: 2020-01-21 12:54:40.316 -0700
OS Version: Mac OS X 10.15.2 (19C57)
Report Version: 12
Anonymous UUID: F8B6954A-8DB8-8EE4-FAB0-89F77F477176

Time Awake Since Boot: 750 seconds

System Integrity Protection: disabled

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000052293882
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [952]

VM Regions Near 0x52293882:
–>
__TEXT 0000000103a07000-0000000104c00000 [ 18.0M] r-x/rwx SM=COW /Volumes/VOLUME/*/ArGest Backup 4.0.debug.app/Contents/MacOS/ArGest Backup 4.0.debug

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 XojoFramework 0x00000001051e5dd3 0x10504f000 + 1666515
1 XojoFramework 0x00000001051e12e3 0x10504f000 + 1647331
2 XojoFramework 0x00000001051dcfb3 DSDelegate::DebuggerConnectionMessage(DebuggerPacketParser const&) + 17
3 XojoFramework 0x00000001051db3ef DebuggerConnection::ProcessMessage(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >) + 67
4 XojoFramework 0x00000001052aa48a TCPSocketConnection::SocketDataReceived(TCPSocket*) + 370
5 XojoFramework 0x000000010516247f TCPSocket::FireEvents() + 123
6 XojoFramework 0x000000010515f0a5 TCPSocketPosix::Poll() + 925
7 XojoFramework 0x00000001051e4176 0x10504f000 + 1659254
8 XojoFramework 0x00000001051e3f8f DebuggerHook + 836
9 ArGest Backup 4.0.debug 0x0000000103cced22 App.Checkappintegrity%b%o + 3186 (/App:267)
10 ArGest Backup 4.0.debug 0x0000000103cc8957 App.Event_Open%%o + 4391 (/App:27)
11 XojoFramework 0x0000000105123b1b CocoaFinishApplicationStartup() + 149
12 XojoFramework 0x00000001051226ce 0x10504f000 + 865998
13 com.apple.CoreFoundation 0x00007fff2ccb4e4a CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 12
14 com.apple.CoreFoundation 0x00007fff2ccb4dde ___CFXRegistrationPost1_block_invoke + 63
15 com.apple.CoreFoundation 0x00007fff2ccb4d53 _CFXRegistrationPost1 + 372
16 com.apple.CoreFoundation 0x00007fff2ccb49a9 ___CFXNotificationPost_block_invoke + 97
17 com.apple.CoreFoundation 0x00007fff2cc84808 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1773
18 com.apple.CoreFoundation 0x00007fff2cc83baf _CFXNotificationPost + 1586
19 com.apple.Foundation 0x00007fff2f32da02 -[NSNotificationCenter postNotificationName:object:userInfo:] + 59
20 com.apple.AppKit 0x00007fff29e7f2ff -[NSApplication _postDidFinishNotification] + 312
21 com.apple.AppKit 0x00007fff29e7f042 -[NSApplication _sendFinishLaunchingNotification] + 208
22 com.apple.AppKit 0x00007fff29e76239 _DPSNextEvent + 1891
23 com.apple.AppKit 0x00007fff29e74690 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
24 XojoFramework 0x00000001051242f5 0x10504f000 + 873205
25 XojoFramework 0x0000000105124339 0x10504f000 + 873273
26 ArGest Backup 4.0.debug 0x0000000103a54d45 Application._CallFunctionWithExceptionHandling%%op + 181
27 XojoFramework 0x00000001052a94bb CallFunctionWithExceptionHandling(void (*)()) + 262
28 XojoFramework 0x00000001051242a2 0x10504f000 + 873122
29 com.apple.AppKit 0x00007fff29e663ae -[NSApplication run] + 658
30 XojoFramework 0x00000001052a782d RuntimeRun + 42
31 ArGest Backup 4.0.debug 0x0000000103b127d3 REALbasic._RuntimeRun + 19
32 ArGest Backup 4.0.debug 0x0000000104ae749e _Main + 846 (/#main:3150)
33 ArGest Backup 4.0.debug 0x0000000104ad9013 main + 19
34 libdyld.dylib 0x00007fff642327fd start + 1
[/code]
I also see similar failures if I remote debug from Mojave to Catalina or Linux to Catalina with the crash always being reported on the Catalina system.

The CheckAppIntegrity() method listed before the debugger lines is a simple shell to check for the existence of all of the proper helpers and environment folders. This is NOT where the built app fails (much further into the process), so I can’t see it having any relationship to the shell tasks being executed.

Are we simply up the proverbial creek with regard to debugging on Catalina, or do any of you have an idea aside from “File a feedback report” (is it worth filing)?

2

My guess is it’s Xojo not the OS. I went back to 2018r3 after having a lot of crashes of 2019 versions. I am running OSX 10.11.6.

Right now I am trying out 2019r3.1. I’ve just had the weirdest crash ever, OSX went down. That doesn’t happen much with (what I consider to be) the most stable operating system there is. That ought to be impossible. I don’t know, I run OSX every day and I work with Xojo every day, and never seen this.

It occurred when my Xojo app, running in the debugger, ran some shell commands. I presume this was what it was doing differently, and perhaps the most likely candidate to explain the crash.

3

Of course you should file a Feedback.

Have you disable the machine’s firewall in System Preferences? Also do you have another machine running Catalina that you can test debugging with?