Yes, I do have the crash report that gets generated by macOS when the application crashes. I haven't reported it anywhere, because this is an old, obsolete version of both the software and the version of Qt that's involved.
I thought about using the 'symbolicatecrash' tool that comes with Xcode, but I've never had any luck getting it to work properly. I suppose I could also use 'atos' to symbolicate line by line, but I don't even know where to begin getting my hands on the dSYM build symbols from the MacPorts build of Qt 5.11. -- Jason Liu On Fri, Sep 1, 2023 at 3:33 PM <chrischa...@gmx.us> wrote: > On 8/31/23 at 6:39 PM, Jason Liu wrote: > > > Does anyone have any objections if I were to resurrect Qt 5.10? One of > the > > ports that I am working on crashes under certain circumstances when using > > qt511, which is the newest Qt that works on macOS 10.11. The version of > Qt > > that was bundled with the pre-built binary distribution was Qt 5.10. > > Admittedly, I am also able to compile the port using qt59, and there are > no > > crashes. In addition, I can also compile the port using qt513 on macOS > > 10.13, and there are also no crashes (qt512 also doesn't currently > exist). > > > > I'm not really sure how much Qt changes with each version. So on the one > > hand, it would be nice to be able to get the port working with the same > > version of Qt that it originally shipped with, but on the other hand, it > > seems like overkill to bring back such a large set of ports as qt510-* > just > > for the sake of a single port on old versions of macOS. > > > > What are everyone's thoughts on this? > > > > -- > > Jason Liu > > > I think it would be much better to investigate the crash first. Do you > have a crash report/have you reported the crash somewhere? >