GNU bug report logs -
#42931
27.1; json-pretty-print-buffer on ~2MB line causes core dump
Previous Next
Reported by: Phil Sainty <psainty <at> orcon.net.nz>
Date: Wed, 19 Aug 2020 13:52:02 UTC
Severity: normal
Found in version 27.1
Done: Paul Eggert <eggert <at> cs.ucla.edu>
Bug is archived. No further changes may be made.
Full log
Message #20 received at 42931 <at> debbugs.gnu.org (full text, mbox):
> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: psainty <at> orcon.net.nz, 42931 <at> debbugs.gnu.org
> Date: Thu, 20 Aug 2020 15:22:31 +0200
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> > looks like stack overflow? I guess the recursive nature of compareseq
> > is got to cause this at some point?
>
> Yup.
>
> I'm not sure what to do about it, though. One easy way to "fix this"
> would be to not use replace-region-contents in json-pretty-print if the
> region is very large... but that's kinda just wallpapering over the
> problem.
>
> replace-region-contents itself could decide to not do all its fancy
> stuff if the region is very large, and just replace the contents in the
> normal way instead?
compareseq is a Gnulib module, so maybe its implementation could be
fixed to bail out when the recursion becomes too deep?
This bug report was last modified 4 years and 268 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.