Custom Query (1030 matches)

At 11/18/2009 03:43 AM, Gary Byers wrote:

The :PREPEND-KERNEL option to SAVE-APPLICATION sets the execute permission bits on the output file; this is appropriate when the intent is to create an executable file (by prepending the lisp kernel to the heap image), but isn't when the option is used to prepend ELF symbol info for oprofile's benefit. (It seems that the ELF file looks "executable enough" to Linux that it tries to to execute it and segfaults; it'd be nicer and less confusing if attempts to execute the image file just failed like other attempts to execute non-executable files fail.)

One way to address this problem without changing any interfaces would be to have the code that processes the :PREPEND-KERNEL option copy the executable bits from the prepended file to the output file (rather than unconditionally setting them), so that an image with an executable file prepended to it would generally be executable and an image with symbol info prepended to it would generally not be.

I think that this'd be as simple as changing (in OPEN-DUMPLISP-FILE)

    (when prepend-fd
      (setq mode (logior #o111 mode)))

to

    (when prepend-fd
      (let* ((prepend-fd-mode (nth-value 1 (%fstat prepend-fd))))
        (setq mode (logior (logand prepend-fd-mode #o111) mode))))

test ticket for commit hook

See ​http://clozure.com/pipermail/openmcl-devel/2009-November/010735.html