Re: [Rd] segfault on write.dcf with gzfile connection

2005-11-28 Thread Prof Brian Ripley
On Sun, 27 Nov 2005, Seth Falcon wrote: > On 27 Nov 2005, [EMAIL PROTECTED] wrote: > >> Unfortunately va_copy is an ISO C99 function, so not always >> available. >> >> Please do heed the posting guide and give us real details of your OS >> and compiler, as they do matter here (stdarg.h is often >>

Re: [Rd] segfault on write.dcf with gzfile connection

2005-11-27 Thread Seth Falcon
On 27 Nov 2005, [EMAIL PROTECTED] wrote: > Unfortunately va_copy is an ISO C99 function, so not always > available. > > Please do heed the posting guide and give us real details of your OS > and compiler, as they do matter here (stdarg.h is often > compiler-specific). > R.version

Re: [Rd] segfault on write.dcf with gzfile connection

2005-11-27 Thread Prof Brian Ripley
Unfortunately va_copy is an ISO C99 function, so not always available. Please do heed the posting guide and give us real details of your OS and compiler, as they do matter here (stdarg.h is often compiler-specific). On Sat, 26 Nov 2005, Seth Falcon wrote: > I'm seeing a segfault on x86_64 Linux

[Rd] segfault on write.dcf with gzfile connection

2005-11-26 Thread Seth Falcon
I'm seeing a segfault on x86_64 Linux with the following code: desc = read.dcf("BAD") con = gzfile("test.gz", "wt") write.dcf(desc, file=con) close(con) where BAD has a long field (see below for example). The crash happens inside dummy_vfprintf. I think the issue is that the