From ripley at stats.ox.ac.uk  Wed Mar 31 22:45:42 2004
From: ripley at stats.ox.ac.uk (Prof Brian Ripley)
Date: Wed Mar 31 22:45:49 2004
Subject: [Rd] segfault in browseURL()
In-Reply-To: <Pine.SOL.4.20.0403311440050.14643-100000@santiam.dfci.harvard.edu>
Message-ID: <Pine.LNX.4.44.0403312130080.28054-100000@gannet.stats>

With what settings of argument `browser'?

If this is using file associations there is a Windows internal limit (it
designed for files and there is a 264 char path limit on files), so I
don't think you can entirely avoid this, although we can avoid the
segfault.

If you absolutely must have such long URLs, try specifying a browser 
(although you will probably find limits that way too).

As the FAQ asks, we do need a reproducible example to check the fixes.

On Wed, 31 Mar 2004, Jeff Gentry wrote:

> Using Win2K (and reportedly WinXP), when the length of the 'url' string
> >= 280 characters, a segmentation fault occurs.
> 
> This doesn't seem to be affecting unix machines.

It's completely independent code between Unix and Windows.

-- 
Brian D. Ripley,                  ripley@stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford,             Tel:  +44 1865 272861 (self)
1 South Parks Road,                     +44 1865 272866 (PA)
Oxford OX1 3TG, UK                Fax:  +44 1865 272595


[Rd] segfault in browseURL()
Prof Brian Ripley