Well it seems I was wrong and this is a common-or-garden bug. Specifically,
from xauth/gethost.c, starting at line 199:
#ifdef HAVE_STRLCPY
strlcpy(path, fulldpyname, sizeof(path));
#else
strncpy(path, fulldpyname, sizeof(path));
path[sizeof(path) - 1] = '\0';
Klemens Nanni writes:
> On Thu, Oct 17, 2019 at 10:30:54PM +0100, cho...@jtan.com wrote:
> > I don't even know where to begin with this one
> Start with providing a backtrace from the core dump: build xauth with
> debug symbols and reproduce, then inspect with gdb.
>
> Otherwise you're on your
On Thu, Oct 17, 2019 at 10:30:54PM +0100, cho...@jtan.com wrote:
> I don't even know where to begin with this one
Start with providing a backtrace from the core dump: build xauth with
debug symbols and reproduce, then inspect with gdb.
Otherwise you're on your own with this very special setup.
$remote xauth add $var
ssh $remote DISPLAY=$DISPLAY $thing
The strange thing is that with a few identical VMs running on this host, only
on one of them does xauth segfault. All have today been upgraded to 6.6 and the
fault was present on 6.5 too (I ignored it because I don't really need X
4 matches
Mail list logo
