Re: Occasionally fatal bug in handler.c?

On 2003-02-26, mutt <at> garydjones.mailshell.com wrote:
> Is there a potential buffer overrun in mutt_decode_xbit? It seems that
> in some circumstances the variable 'l' indicating the position at
> which to insert a character into the buffer may not be changed on
> return from convert_to_state (with disastrous results), at least
> that's what it looks like from my debugging but then I'm trying to do
> it with dprint which doesn't exactly make life easy.

Can you describe the circumstances under which you believe an overflow
might occur?  It looks to me like the only case in which 'l' is not set
upon return is when 'bufi' is NULL, which is the final call from
mutt_decode_xbit and thus 'l' is no longer used.