similar to: sweave provoked segfault (PR#2809)

The released version of R-1.7.0 builds and checks fine on Mandrake 9.1, but I am still having trouble with my vignettes and sweave causing segfaults. Unfortunately the segfaults with the release version are happening in tests where I have much more difficulty trapping them. I did also build R-1.7.0beta_2003-04-16 this morning, and for that the segfaults occurred in a test which is much easier for

I always forget those CC's :(( ---------- Forwarded message ---------- Date: Tue, 22 Aug 2000 18:39:14 +0200 (CEST) From: Igmar Palsenberg <i.palsenberg at jdimedia.nl> To: zack at wolery.cumb.org Subject: Re: Work around Linux kernel bug provoked by nchan.c Hi, Regarding this bug : the man page states : On success, zero is returned. On error, -1 is returned and errno is set

The Linux implementation of TCP sockets has a bug which causes shutdown(sock, SHUT_RD) to fail spuriously (ENOTCONN) if the write side of the socket has already been shut down. If you are using SSH port forwarding to tunnel HTTP through a firewall, nchan.c will tickle this bug once for every HTTP exchange. You will therefore get lots of useless, annoying error messages: channel 2:

I'm doing some work in C with the R_ExternalPointer interface, and having some seg fault problems. I expect the crash is my fault, bad pointer in my code causing a fault later etc, but I'm curious about the point of failure. R almost always falls over in a call to unzReadCurrentFile following a burst of disk activity. I'm definitely not doing anything that would call that

https://bugs.freedesktop.org/show_bug.cgi?id=66642 Priority: medium Bug ID: 66642 Assignee: nouveau at lists.freedesktop.org Summary: [nva5] Wrong provoking vertex is selected for flat attribute interpolation (clipping?) Severity: normal Classification: Unclassified OS: Linux (All) Reporter:

I believe https://reviews.llvm.org/D44449 <https://reviews.llvm.org/D44449> should fix this issue. Thanks, Volodymyr > On Apr 2, 2018, at 22:51, Shoaib Meenai via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > Adding cfe-dev, since this is a clang issue. > > From: llvm-dev <llvm-dev-bounces at lists.llvm.org <mailto:llvm-dev-bounces at lists.llvm.org>>

Adding cfe-dev, since this is a clang issue. From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Jim Meyering via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Jim Meyering <jim at meyering.net> Date: Monday, April 2, 2018 at 8:40 PM To: "llvm-dev at lists.llvm.org" <llvm-dev at lists.llvm.org> Subject: [llvm-dev] trivial input provokes failed

While attempting to reduce a ubsan-specific bug, I stumbled upon the following. [I would have filed a bug report, but don't have an account, and so requested one per https://bugs.llvm.org/ about 7 hours ago -- but still no response, so am sending this instead. ] Using clang built from latest master of about 5 hours ago: $ echo struct a typename a | clang -x c++ - <stdin>:1:19: error: