GNU bug report logs - #56443
28.1; Mac segmentation fault with ffap

Previous Next

Package: emacs;

Reported by: Stephen Eglen <sje30 <at> cam.ac.uk>

Date: Thu, 7 Jul 2022 17:23:02 UTC

Severity: normal

Found in version 28.1

Done: Mattias Engdegård <mattiase <at> acm.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Daniel Martín <mardani29 <at> yahoo.es>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 56443 <at> debbugs.gnu.org, sje30 <at> cam.ac.uk
Subject: bug#56443: 28.1; Mac segmentation fault with ffap
Date: Fri, 08 Jul 2022 11:54:04 +0200
Eli Zaretskii <eliz <at> gnu.org> writes:

>
> That's not NULL, that's nil (which is represented as zero).
>
> But I don't understand how could that happen, because
> Ffile_name_case_insensitive_p checks the argument for validity:
>
>   DEFUN ("file-name-case-insensitive-p", Ffile_name_case_insensitive_p,
> 	 Sfile_name_case_insensitive_p, 1, 1, 0,
> 	 doc: /* Return t if file FILENAME is on a case-insensitive filesystem.
>   Return nil if FILENAME does not exist or is not on a case-insensitive
>   filesystem, or if there was trouble determining whether the filesystem
>   is case-insensitive.  */)
>     (Lisp_Object filename)
>   {
>     Lisp_Object handler;
>
>     CHECK_STRING (filename);  <<<<<<<<<<<<<<<<<<<<<<<<<<<<
>     filename = Fexpand_file_name (filename, Qnil);
>
> So it seems like expand-file-name returned nil in this case?
>
> Can someone step through the code, including stepping into
> Fexpand_file_name, and see  how we get that nil in this case?
>
> (I tried to reproduce on my system, which is not a Mac, but I don't
> see any nil filenames in that case.)

Apparently it comes from the "parent" variable, which is the result of
the file_name_directory call:

Process 61514 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
    frame #0: 0x000000010064fefc emacs`Ffile_name_case_insensitive_p(filename=0x000000011534dc44) at fileio.c:2608:18
   2605		 (impossible?).  */
   2606	      if (!NILP (Fstring_equal (parent, filename)))
   2607		return Qnil;
-> 2608	      filename = parent;
   2609	    }
   2610	}
   2611
Target 0: (emacs) stopped.
(lldb) fr v parent
(Lisp_Object) parent = NULL

Is the following expression the correct way to manually interpret the
Lisp_Object as a Lisp_String?  (where $ptr is the memory address of
"filename" in this scenario):

(char *) ((struct Lisp_String *)$ptr)->u.s.data

That prints an empty string in LLDB.

BTW, I don't really understand the semantics of
file-name-case-insensitive-p.  The docstring says that it returns nil if
the file is not found, but these calls return t on my system:

(file-name-case-insensitive-p "")
(file-name-case-insensitive-p "FileThatDoesNotExist")

Does that make sense?




This bug report was last modified 3 years and 13 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.