Re: emacs crashes with eval-region and marker

[Lute Kamstra]

Stefan Monnier <address@hidden> writes:

>> +    int marker_pos = -1;
>
> This should be EMACS_INT, since Lisp_Object can be 64bit even if int is
> only 32bit 

I just checked:

  /* Return the char position of marker MARKER, as a C integer.  */

  int
  marker_position (marker)
       Lisp_Object marker;
  {

and figured it should be an int.

> (and it should be in the MARKERP branch of PRINTPREPARE rather than
> in PRINTDECLARE).

Ah yes, of course.

> PS: Yes, it's a very widespread problem, but if we ever want to be able to
>     handle >2GB buffers, we should start thinking about it.

I'll be happy to start the habit of using EMACS_INT.

Lute.