[Cin] executable stacks are bad...m-kay?

[Rob Prowel]

Thought this went away in my Jan-2023 git pull, but apparently not. 
Looked in my dmesg output and saw this again.

process 'sharebin/cingg2301/bin/cin' started with executable stack

Why?  A consequence of the plug-in system? a poorly designed 3rdparty 
library? an oversight?

stack segments are generally marked as no-exec to protect against using 
them to execute rogue instructions by saving those instructions in 
auto-vars on the stack that could be executed by fudging the return 
address of a function.

Just looking for an acknowledgement of this, and any relevant related 
history at this point.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x36472CAD382840B8.asc
Type: application/pgp-keys
Size: 632 bytes
Desc: OpenPGP public key
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20230111/dac8d736/attachment.skr>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 236 bytes
Desc: OpenPGP digital signature
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20230111/dac8d736/attachment.sig>