[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#6378: all-completions Segfault
From: |
Lennart Borgman |
Subject: |
bug#6378: all-completions Segfault |
Date: |
Tue, 8 Jun 2010 21:32:11 +0200 |
On Tue, Jun 8, 2010 at 9:08 PM, Juanma Barranquero <lekktu@gmail.com> wrote:
> On Tue, Jun 8, 2010 at 20:58, Lennart Borgman <lennart.borgman@gmail.com>
> wrote:
>
>> Isn't there a similar case in Ftry_completion?
>
> Apparently no.
>
> ELISP> (try-completion "" [])
> *** Eval error *** Wrong type argument: vectorp, []
> ELISP> (try-completion "" [[]])
> *** Eval error *** Bad data in guts of obarray
> ELISP> (try-completion "" [0])
> nil
> ELISP> (try-completion "" [a])
> ""
> ELISP>
>
> Juanma
So the thing protecting it is that an obarray can't have length 0? Can
one be sure that does not break someday?
bug#6378: all-completions Segfault, Lawrence Mitchell, 2010/06/08
- bug#6378: all-completions Segfault, Stefan Monnier, 2010/06/08
- bug#6378: all-completions Segfault, Thierry Volpiatto, 2010/06/09
- bug#6378: all-completions Segfault, Thierry Volpiatto, 2010/06/09
- bug#6378: all-completions Segfault, Lennart Borgman, 2010/06/09
- bug#6378: all-completions Segfault, Thierry Volpiatto, 2010/06/09
- bug#6378: all-completions Segfault, Lennart Borgman, 2010/06/09
- bug#6378: all-completions Segfault, Thierry Volpiatto, 2010/06/09
- bug#6378: all-completions Segfault, Andreas Schwab, 2010/06/09