lynx-dev exit_immediately_with_error_message (was Fatal error in 2.8.2rel.1)

[Klaus Weide]

On Sat, 9 Oct 1999, Leonid Pauzner wrote:

> 9-Oct-99 02:24 Klaus Weide wrote:
> 
> > The new 2.8.3dev code still has a problem though: near the end,
> 
> Yes/no. (This will not happen since "state" assumed to have only two states.
> And the above fix could probably be easier fixed with setting buf2 to "\0"
> after if (first_file) when buf2 got no message - not a large overhead before
> exit() anyway. Sorry for bad design, that was a 'last minute changes').

The printf/fprintf problem does exist though: try something like

   lynx gopher://localhost/foo%s%s%s%s%sbar

(assuming you have no gopher server running on localhost, and gopher
compiled into lynx).  I get either Fatal error or garbage in the
displayed message.

  Klaus