Using TOOL / Configure Tool I added a new voice on normale IDE (Rad Studio 12.3 32 bit version) to sign a builded project (it calls SignotaurTool client).
All works perfect !!! But When I use it in the 64 bit version of the IDE an exception were thrown by IDE:
Access violation in RTL1290.bpl
The excetpion seems to be about “RtlWow64GetCurrentCpuArea” that is called from “someone” and that is for ARM32 platform (???)
The strange thing is that this occurs only when you try to sign (and only in 64bit IDE) … if you put in the parameters line only -h for example there is no exception (so, really from RTL290 or from something about Signotaur ?)
This is the parameters line of the “configure tool” (with reserved data masked of course):
I can reproduce the error here, it’s a bug in the RAD Studio 64bit IDE, definitely not a Signotuar issue. The 12.3 64bit IDE is an “Initial Release” which IMHO is BETA quality - there are still lots of issues with it. It’s good enough for library vendors to test with, but not yet good enough for production use.
[00007FF81444C25F]{rtl290.bpl } System.@UStrAsg + $5F
[00000000710DADC8]{exceptiondiag290.bpl} Jcldebug.JclCreateStackList + $48
[00000000710DAB56]{exceptiondiag290.bpl} Jcldebug.Unknown function at JclValidateModuleAddress + $186
[00000000710DD81F]{exceptiondiag290.bpl} Jcldebug.Unknown function at AddModule + $AF
[00000000710C2465]{exceptiondiag290.bpl} Unknown function at _ZTRN13Jclhookexcept15TJclModuleArrayE + $B15
[00000000710C26AC]{exceptiondiag290.bpl} Unknown function at _ZTRN13Jclhookexcept15TJclModuleArrayE + $D5C
[00000000710C2877]{exceptiondiag290.bpl} Unknown function at _ZTRN13Jclhookexcept15TJclModuleArrayE + $F27
[00007FF814449E37]{rtl290.bpl } System.@DelphiExceptionHandler + $267
[00007FF8DAAC66AF]{ntdll.dll } Unknown function at __chkstk + $9F
[00007FF8DA9E9CD7]{ntdll.dll } Unknown function at RtlWow64GetCurrentCpuArea + $C17
[00007FF8DAAC5FEE]{ntdll.dll } KiUserExceptionDispatcher + $2E
[00007FF81444C25F]{rtl290.bpl } System.@UStrAsg + $5F
[000000007298C7F5]{coreide290.bpl} Uiutils.ExpandRootMacro + $35
[0000000072AC920C]{coreide290.bpl} Transfer.ExecuteTransferItemName + $23C
[000000000076D46C]{bds.exe } Unknown function at __dbk_fcall_wrapper + $10B5CC
[00007FF81454F80B]{rtl290.bpl } System.Rtti.RawInvoke + $6B
[00007FF81454FD7D]{rtl290.bpl } System.Rtti.Invoke + $31D
[00007FF814540044]{rtl290.bpl } System.Rtti.TRttiInstanceMethodEx.DispatchInvoke + $7C4
[00007FF8145503BD]{rtl290.bpl } System.Rtti.TRttiMethod.Invoke + $5D
[00000000007B3B96]{bds.exe } Unknown function at __dbk_fcall_wrapper + $151CF6
[000000000076F026]{bds.exe } Unknown function at __dbk_fcall_wrapper + $10D186
[00007FF8145F0ED7]{rtl290.bpl } System.Classes.TBasicAction.Execute + $27
With other programs (I tried notepad too) I had not issue.
But like you told it is only a preliminary works.
I use it 'cause at the end, after lot of years, I can debug a dll (made with C++) called from Delphi.
The thing that interests me most is that it was not a “hidden” problem of SignoTaur.
I compile the final production with the 32-bit version of the IDE, and then sign the programs from there.