[Interest] crahs with macdeployqt

Fri Nov 29 17:04:07 CET 2024

Hi Robert,

>>you are not missing deep signing after macdeployqt, aren't you?

in fact I did not sign the binary because I had a problem with the signing itself: If I sign the camera.app example via:

codesign --options=runtime --deep ./camera.app -s "Developer ID Application: AlexC (xzy)"

and then check via

codesign --verify --deep --strict --verbose=2 ./camera.app   

I get

./camera.app: invalid signature (code or signature have been modified)
In subcomponent: /Users/soulalex/Qt6_8/Examples/Qt-6.8.0/multimedia/camera/camera.app/Contents/PlugIns/imageformats/libqgif.dylib
In architecture: arm64

It had been workling for years on an older Intel Mac but just recently I updated to an M1 and here the problem with the signature came up.

So – does macdeployqt without signing lead to a crash in any case and my problem is maybe purely related to a codesign issue ?

Best

Alex

--
http://www.carot.de
Email : Alexander at Carot.de
Tel.: +49 (0)177 5719797

> Gesendet: Freitag, 29. November 2024 um 09:03
> Von: coroberti <coroberti at gmail.com>
> An: "Alexander Carôt" <alexander_carot at gmx.net>
> CC: "interest at qt-project.org" <interest at qt-project.org>
> Betreff: Re: [Interest] crahs with macdeployqt
>
> Alexander,
> Additionally to Hamish's suggestion,
> you are not missing deep signing after macdeployqt, aren't you?
> 
> Kind regards,
> Robert Iakobashvili
> ............................
> 
> On Fri, Nov 29, 2024 at 8:49 AM Hamish Moffatt via Interest
> <interest at qt-project.org> wrote:
> >
> > Ouch. Check out this thread I found by searching on the missing path text: https://developer.apple.com/forums/thread/764315
> >
> > Hamish
> >
> > Sent from Nine
> > ________________________________
> > From: Alexander Carôt <alexander_carot at gmx.net>
> > Sent: Friday, November 29, 2024 17:42
> > To: Hamish Moffatt; interest at qt-project.org
> > Subject: Aw: Re: [Interest] crahs with macdeployqt
> >
> > >>> What does the crash log say?
> >
> > This is it – looks it's related to a path and/or code signature issue:
> >
> >
> >
> > Exception Type:  EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
> > Exception Subtype: UNKNOWN_0x32 at 0x0000000100978000
> > Exception Codes: 0x0000000000000032, 0x0000000100978000
> > VM Region Info: 0x100978000 is in 0x100978000-0x100998000;  bytes after start: 0  bytes before end: 131071
> >       REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
> >       UNUSED SPACE AT START
> > --->  __TEXT                      100978000-100998000    [  128K] r-x/r-x SM=COW  /main_executable_path_missing
> >       __DATA_CONST                100998000-10099c000    [   16K] rw-/rw- SM=COW  /main_executable_path_missing
> > Termination Reason: CODESIGNING 2 Invalid Page
> >
> > Triggered by Thread:  0
> >
> > Thread 0 Crashed:
> > 0   dyld_path_missing                           0x100cf21e4 0x100cf0000 + 8676
> > 1   dyld_path_missing                           0x100cf426c 0x100cf0000 + 17004
> > 2   dyld_path_missing                           0x100d3e6fc 0x100cf0000 + 321276
> > 3   dyld_path_missing                           0x100cf5e3c 0x100cf0000 + 24124
> >
> >
> > Thread 0 crashed with ARM Thread State (64-bit):
> >     x0: 0x0000000100978000   x1: 0x000000016f487558   x2: 0x000000016f487500   x3: 0x0000000100cf1e24
> >     x4: 0x0000000000000001   x5: 0x0000000000000073   x6: 0x0000000000000000   x7: 0x0000000000000e60
> >     x8: 0x000000016f487538   x9: 0x0000000100d77458  x10: 0x0000000100d61000  x11: 0x0000000100d6ea56
> >    x12: 0x0000000000000065  x13: 0x0000000000000073  x14: 0x000000000004bca0  x15: 0x0000000000000000
> >    x16: 0x0000000100cf430c  x17: 0x6ae100016f487500  x18: 0x0000000000000000  x19: 0x000000016f487558
> >    x20: 0x0000000100978000  x21: 0x000000016f487500  x22: 0x000000016f487840  x23: 0x0000000000000000
> >    x24: 0x0000000000000000  x25: 0x0000000000000000  x26: 0x0000000000000000  x27: 0x0000000000000000
> >    x28: 0x0000000000000000   fp: 0x000000016f4874f0   lr: 0x0000000100cf426c
> >     sp: 0x000000016f487460   pc: 0x0000000100cf21e4 cpsr: 0x80001000
> >    far: 0x0000000100978000  esr: 0x92000007 (Data Abort) byte read Translation fault
> >
> > Binary Images:
> >        0x100cf0000 -        0x100d73fff dyld_path_missing (*) <40bedd20-da23-3b70-a9c2-a1c68a738762> /dyld_path_missing
> >        0x100978000 -        0x100997fff main_executable_path_missing (*) <cfe71e9e-9cc2-3553-bbe2-f2ed3a87dd7a> /main_executable_path_missing
> >                0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???
> >
> >
> >
> > --
> > http://www.carot.de
> > Email : Alexander at Carot.de
> > Tel.: +49 (0)177 5719797
> >
> >
> > > Gesendet: Donnerstag, 28. November 2024 um 22:53
> > > Von: "Hamish Moffatt via Interest" <interest at qt-project.org>
> > > An: interest at qt-project.org
> > > Betreff: Re: [Interest] crahs with macdeployqt
> > >
> > > On 29/11/24 07:01, Alexander Carôt via Interest wrote:
> > > > Hello all,
> > > >
> > > > I have a strange effect with Qt6.8 on a Mac M1 (with macOS 15.0.1) regarding macdeployqt.
> > > >
> > > > Whatever binary I use (including the examples such as “camera” in multimedia) it crashes after running macdeployqt on it.
> > > >
> > > > Before I probably reinstall Qt (or maybe an older version of it) I wonder if you have better idea to approach this issue.
> > > >
> > >
> > > What does the crash log say?
> > >
> > >
> > > Hamish
> > >
> > > _______________________________________________
> > > Interest mailing list
> > > Interest at qt-project.org
> > > https://lists.qt-project.org/listinfo/interest
> > > </interest at qt-project.org></cfe71e9e-9cc2-3553-bbe2-f2ed3a87dd7a>
> > _______________________________________________
> > Interest mailing list
> > Interest at qt-project.org
> > https://lists.qt-project.org/listinfo/interest
> </alexander_carot at gmx.net></interest at qt-project.org></interest at qt-project.org></alexander_carot at gmx.net></coroberti at gmail.com>