Okay, that just got interesting.

GhostScript invocation with tup crashes with the following error message:
"*** C stack overflow. Quiting..."
(( : foreach *.ps |> "C:\Program Files\gs\gs9.54.0\bin\gswin64c.exe" 
-dNOSAFER -dNOPAUSE -dBATCH -dAutoRotatePages=/None -dPrinted=false 
-sDEVICE=pdfwrite -o %o %f |> %B.pdf ))

Checked with both 'gswin64' and 'gswin64c' from the standalone distribution 
( version string is: "GPL Ghostscript 9.54.0 (2021-03-30)" ).
Direct invocations succeed.

As customary, here's the ProcMon log: https://yadi.sk/d/ob7vYjZJi2brRg
воскресенье, 26 сентября 2021 г. в 16:54:57 UTC+3, [email protected]: 

> On Sat, Sep 25, 2021 at 7:16 AM kmickle <[email protected]> wrote:
>
>> Gave it a run. The following happened: tup did not block GhostScript, and 
>> it terminated correctly. However, tup was unable to detect the files GS 
>> wrote to, so the build recipe failed.
>> It seems the hook on GS is now non-functional. 
>>
>> Here's the trace:
>> https://yadi.sk/d/niplINUFbxnONw
>>  
>
>
> You're still expecting the output to be test.pdf, right? I see lilypond 
> call SetRenameInformationFile (or really NtSetInformationFile with 
> FileInformationClass == FileRenameInformation) to rename a temporary file 
> to c:\test\test.pdf. Tup should be hooking that function, and I do see the 
> write to c:\test\.tup\tmp\deps-3035 after that call, which should be when 
> it is saving the file info. I'm a bit stumped why that wouldn't be working 
> now.
>
> Does calling ghostscript directly work for you, or does that fail to 
> detect the output too? Here are the rules I was testing with:
>
> : ok.ps |> gswin32 -dNOSAFER -dNOPAUSE -dBATCH -dAutoRotatePages=/None 
> -dPrinted=false -sDEVICE=pdfwrite -o %o %f |> test-gswin32.pdf ^/gswin32.ini
> : ok.ps |> gswin64 -dNOSAFER -dNOPAUSE -dBATCH -dAutoRotatePages=/None 
> -dPrinted=false -sDEVICE=pdfwrite -o %o %f |> test-gswin64.pdf ^/gswin64.ini
>
> With the older version, both failed with the hang that you described. With 
> the one I posted (v0.7.11-50 or later), both succeed (and detect the file 
> writes).
>
> -Mike
>

-- 
-- 
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tup-users/8905209b-ebc3-4d04-acd3-0d9f6a7ba09dn%40googlegroups.com.

Reply via email to