Where to look for evidence of a code signing issue

I have compiled and am running an executable for creating and editing schematic diagrams. The main UI window, invoked from the terminal, launches and runs under XQuartz. However, when I try to launch another schematic window from the existing one, a fatal error is reported in trying to spawn the process. The message is not very descriptive:

bash-3.2$ ./xschem
% EMERGENCY SAVE DIR: /tmp/xschem_emergencysave_untitled_HVYd8RkFov

FATAL: signal 4
while editing: untitled

There's no problem with this operation if the executable is compiled and run in debian linux. So - my question is - if this is a code signing issue related to a process spawning a process, where do I look for evidence of that? I don't see any evidence in the syslog. Presumably there's a log where this is reported.

OS: 10.15.7, iMac13,2
Does this generate a crash report? If so, please post it here. Use the text attachment feature (the paperclip icon) to avoid clogging up the timeline.

Oh, and you tagged your question with App Sandbx. Does that mean that your main app is sandboxed?

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Where to look for evidence of a code signing issue
 
 
Q