Chronological Thread 

< Chronological >      < Thread >

---

On Mon, Jun 18, 2007 at 04:50:14PM +0100, Jeremy Henty wrote:
> When I press F1 TeXmacs does nothing except dump some errors to
> standard output. If I press F1 again it segfaults.
>
> The problem appears to be the literal strings "No matches found
> for#\`\`" and "Results of the search for#\`\`" in
> progs/doc/docgrep.scm . Guile rejects the "\`" as invalid read
> syntax.
>
> Is there any reason not to hack those strings so as to read "No
> matches found for ``" and "Results of the search for ``"? It's not
> clear to me what the point of the "#\`\`" syntax is anyway.
>
> (In case you're wondering why I didn't just try it, well I did and
> promptly hit another bug (to be reported separately), so I don't know
> whether my hacked strings will give sensible results.)
>
> I suspect that this is an incompatibility between Guile 1.6 and Guile
> 1.8; the 1.6 documentation suggests that \ escapes any character
> whereas 1.8 explicitly lists the valid \<char> escape sequences. I've
> searched the rest of the TeXmacs scheme files and these two strings
> are the only ones that use invalid \-escapes.
>
> I'm running TeXmacs 1.0.6.10 on Guile 1.8.1 . I've appended the full
> transcript (with backtrace enabled).

Strange, in the CVS version the #\`#\` characters have been changed into ``.
No idea why this did not go into version 1.0.6.10. Anyway, things should
be fine for the next version 1.0.6.11. If not, then please let know.

Best wishes, Joris

---

• SegFault from bad strings in TeXmacs/progs/doc/docgrep.scm (Guile-1.8 incompatibility?), Jeremy Henty, 06/18/2007
  • Re: [TeXmacs] SegFault from bad strings in TeXmacs/progs/doc/docgrep.scm (Guile-1.8 incompatibility?), Joris van der Hoeven, 06/18/2007
    • Re: [TeXmacs] SegFault from bad strings in TeXmacs/progs/doc/docgrep.scm (Guile-1.8 incompatibility?), Jeremy Henty, 06/18/2007

---

Archive powered by MHonArc 2.6.19.