Pike-devel February 2005

pike-devel@lists.lysator.liu.se

8 participants
24 discussions

The joy of new tools
by Peter Bortas ＠ Pike developers forum 11 Feb '05

11 Feb '05

Both 7.6 and 7.7-comiplations give me this on an up to date Debian unstable: sed -e 's/YY_COUNT_TYPE/unsigned int/' \ -e 's/YY_FROM_CONST/const/' \ < /pkg/pike/src/Pike/7.6/src/y.tab.c > /pkg/pike/src/Pike/7.6/src/language.c Compiling /pkg/pike/src/Pike/7.6/src/language.c y.tab.c:384: error: two or more data types in declaration of `yyss' y.tab.c:921: error: two or more data types in declaration of `yyr1' y.tab.c:1059: error: two or more data types in declaration of `yydefact' *and so on*

4 4

on the subject of segfaults
by Martin Bähr 09 Feb '05

09 Feb '05

hi, the following was reported on irc. this code causes a segfault on pike 7.6: void main() { object data = Web.RDF()->parse_xml(Stdio.read_file("data.xml")); array link_temp = map(indices(data->get_subject_map()),"get_uri"); //array link_temp = indices(data->get_subject_map())->get_uri; } what is interresting to note is that using the commented line instead, no segfault happens. should those two lines not be compiled to the same? the segfault appeas to happen while the function that contains these lines, returns. (in this case when main() returns) data.xml is attached. greetings, martin.

2 2

(segfault);
by Tobias Josefowitz 08 Feb '05

08 Feb '05

after accidentally casting an int to a "flot" in hilfe, it segfaulted. so i played around: Pike v7.6 release 24 running Hilfe v3.5 (Incremental Pike Frontend) > (embee); Segmentation fault 17:16 ~ KingOfPrussia) pike -e '(embee);' -:2:Undefined identifier "embee". Segmentation fault 17:17 ~ KingOfPrussia) cat yikes.pike int main() { (embee); } 17:17 ~ KingOfPrussia) pike yikes yikes.pike:2:Undefined identifier "embee". Segmentation fault 17:17 ~ KingOfPrussia) uname -a Linux KingOfPrussia 2.6.10-gentoo-r4 #1 Mon Jan 10 18:46:07 CET 2005 i686 AMD Athlon(tm) Processor AuthenticAMD GNU/Linux

2 1

filesystem_stat issue (Linux, 2.6 kernel)
by David Hedbor ＠ Pike developers forum 01 Feb '05

01 Feb '05

fileystem_stat is not working correctly with NFS filesystems under Linux (at least kernel v2.6, glibc 2.3.4). Specifically block size is not correct. In my case I get blocksize 4096 while in actuality the block size is 32768. The 4096 is, according to the Linux statvfs manual page, the fragment size. I don't know if this is a Linux specific issue, but it might be (google says this field is "fundamental block size" in various UNIX flavors, but it's unclear to me what that means). Anyhow, the app below works correctly under Linux, but I don't know if it works on other systems. #include <sys/vfs.h> /* or <sys/statfs.h> */ #include <sys/statvfs.h> #include <stdio.h> int main(int argc, char *argv[]) { struct statvfs st; if(argc != 2) { return 1; } statvfs(argv[1], &st); printf("Free blocks: %d, Blocksize: %ld, fragment size: %ld, Free GB: %f\n", (int)st.f_bavail, st.f_bsize, st.f_frsize, ((float)st.f_bavail * st.f_bsize) / (1024.0 * 1024.0 * 1024.0)); return 0; }

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel February 2005