Description of problem: I get a segfault with: plot 'bug.data' using 6:($210-$95) I'll attach my data file bug.data. This is very strange. Backtrace is: (gdb) run Starting program: /usr/bin/gnuplot bug-temp.plt Program received signal SIGSEGV, Segmentation fault. *__GI_wmemset (s=0xbf959990, c=48, n=4294964831) at wmemset.c:33 33 wp[0] = c; (gdb) bt #0 *__GI_wmemset (s=0xbf959990, c=48, n=4294964831) at wmemset.c:33 #1 0x00b8193b in ___printf_fp (fp=0x30, info=0x30, args=0x30) at printf_fp.c:1088 #2 0x00000030 in ?? () #3 0x00000030 in ?? () #4 0x00000030 in ?? () #5 0x00000030 in ?? () ....... until infinity. I tried with FC6 gnuplot, same thing. That's a bit strange and it may not be a gnuplot bug but an issue with my libs or something like that. I run fedora devel. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 152147 [details] data file that triggers the segfault
Fedora 7 test bugs should be filed against "devel", not against test1/2/3. This isn't obvious, I know. Moving this report so it isn't lost. This is a bulk message -- I apologize if this was actually meant to be targeted against a different release. If so, please fix or let me know. Thanks.
There seems to be problem with gprintf(util.c) procedure - the segfault happens when program try to write double variable (x), in format "%g" which should cause no error. Jakub, could you please look at it.
This is a glibc bug, reproduced with current CVS glibc built for i686, using union { long long l; double d } u = { .l = 0x3f1a36e2eb1c432cLL }; int main (void) { __builtin_printf ("%g\n", u.d); return 0; }
http://sources.redhat.com/ml/libc-hacker/2007-04/msg00005.html
*** Bug 236536 has been marked as a duplicate of this bug. ***
Should be fixed in glibc-2.5.90-21.
I can confirm my case to be fixed with -21 (bug 236536).
Fixed for my case too.