pike issueshttps://git.lysator.liu.se/pikelang/pike/-/issues2009-04-16T14:11:39Zhttps://git.lysator.liu.se/pikelang/pike/-/issues/4209Stdio.file_size reports wrong size for directories2009-04-16T14:11:39ZPeter BortasStdio.file_size reports wrong size for directoriesImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4209
Reported by Leif Andersson, LTH Reglerteknik <leif@control.lth.se>
The documentation for Stdio.file_size states:
//! Give the size of a file. Size -1 indicates that...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4209
Reported by Leif Andersson, LTH Reglerteknik <leif@control.lth.se>
The documentation for Stdio.file_size states:
//! Give the size of a file. Size -1 indicates that the file either
//! does not exist, or that it is not readable by you. Size -2
//! indicates that it is a directory, -3 that it is a symlink and -4
//! that it is a device.
//!
The snapshot of 7.7, that I took a few days ago, however, does not give -2
for a directory, but rather the same size as reported by ls -l.
The test script, named prov.pike is:
```
//======== prov.pike =========================
int size;
string filename;
int main() {
filename = "prov.pike";
size = Stdio.file_size(filename);
write("%s size = %d\n", filename,size);
filename = "nisse.nisse";
size = Stdio.file_size(filename);
write("%s size = %d\n", filename,size);
filename = "pike";
size = Stdio.file_size(filename);
write("%s size = %d\n", filename,size);
```
}
// =========== end prov.pike ==============
============== Test results: =====================
> ls -ld pike prov.pike nisse.nisse
ls: nisse.nisse: No such file or directory
drwxr-xr-x 3 leif dip 4096 12 jul 18.29 pike/
-rw-r--r-- 1 leif dip 369 20 jul 12.45 prov.pike
> /opt/pike/7.7.25/bin/pike prov.pike
prov.pike size = 369
nisse.nisse size = -1
pike size = 4096
>
============= Specifications: =============
> head -1 /etc/issue
Fedora Core release 5 (Bordeaux)
```
> uname -srv
Linux 2.6.17-1.2145_FC5smp #1 SMP Sat Jul 1 13:19:14 EDT 2006
> cat buildid.txt
Pike export stamp
time:1152866217
major:7
minor:7
build:25
year:2006
month:07
day:14
hour:08
minute:36
second:57
>
```
======== Other comments ================
Other versions of Pike, including the current stable version 7.6.86, give
results according to the documentation. This version compiled on an FC4
gives the same erroneous result.Pike 7.8https://git.lysator.liu.se/pikelang/pike/-/issues/4206ODBC: Column names are truncated2009-04-16T14:11:39ZPeter BortasODBC: Column names are truncatedImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4206
Reported by Marcus Wellhardh <wellhard@roxen.com>
When using an ODBC connection to an msSQL server the column names are
truncated. It is porbably related to the adde...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4206
Reported by Marcus Wellhardh <wellhard@roxen.com>
When using an ODBC connection to an msSQL server the column names are
truncated. It is porbably related to the added unicode support.
Example (pike from 4.5.78):
```
Pike v7.4 release 398 running Hilfe v3.5 (Incremental Pike Frontend)
> object db=Sql.sql("odbc://test:test@groept");
>
> mixed res = db->query("select * from person");
> werror("%O", res);
({ /* 3 elements */
([ /* 6 elements */
".firs":"Yuri",
".last":"Cauwerts",
".pers":"1",
"firs":"Yuri",
"last":"Cauwerts",
"pers":"1"
]),
```
It has however worked before (pike from 4.0.425):
```
Pike v7.4 release 340 running Hilfe v3.5 (Incremental Pike Frontend)
> object db=Sql.sql("odbc://test:test@groept");
> mixed res = db->query("select * from person");
> werror("%O", res);
({ /* 3 elements */
([ /* 6 elements */
".firstname":"Yuri",
".lastname":"Cauwerts",
".personid":"1",
"firstname":"Yuri",
"lastname":"Cauwerts",
"personid":"1"
]),
```Pike 7.4Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/4173double free from las2009-04-16T14:11:39ZPeter Bortasdouble free from lasImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4173
Reported by Martin Nilsson, IDA <nilsson@pike.ida.liu.se>
The code
```
array x =
# 1 "/home/nilsson/xx"
({
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, ...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4173
Reported by Martin Nilsson, IDA <nilsson@pike.ida.liu.se>
The code
```
array x =
# 1 "/home/nilsson/xx"
({
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1,
1, 1
})
# 1 "x"
;
```
results in
*** glibc detected *** corrupted double-linked list: 0x082fa4c0 ***
```
Program received signal SIGABRT, Aborted.
[Switching to Thread -1210734912 (LWP 20468)]
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7d839d1 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7d852e9 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0xb7db770a in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6
#4 0xb7dbe172 in malloc_trim () from /lib/tls/i686/cmov/libc.so.6
#5 0xb7dbe2ea in free () from /lib/tls/i686/cmov/libc.so.6
#6 0x0809a88a in really_free_array (v=0xb7e84ff4)
at /home/nilsson/Pike/7.6/src/array.c:135
#7 0x08141182 in eval (n=Variable "n" is not available.
) at /home/nilsson/Pike/7.6/src/las.c:5542
#8 0x08141a61 in optimize (n=0x8320930)
at /home/nilsson/Pike/7.6/src/las.c:5240
#9 0x08145924 in dooptcode (name=0x82c2b54, n=0x8320840, type=0x82c36d0,
modifiers=1) at /home/nilsson/Pike/7.6/src/las.c:5670
#10 0x08109065 in end_first_pass (finish=1)
at /home/nilsson/Pike/7.6/src/program.c:3087
#11 0x081094ce in debug_end_program ()
at /home/nilsson/Pike/7.6/src/program.c:3198
#12 0x081098fb in run_pass2 (c=0x82fd538)
at /home/nilsson/Pike/7.6/src/program.c:6552
#13 0x08109b1f in compile (aprog=0x82fcc80, ahandler=0x0, amajor=0, aminor=
0,
atarget=0x83173b0, aplaceholder=0x0)
at /home/nilsson/Pike/7.6/src/program.c:6759
#14 0x0814cd3f in f_compile (args=6)
at /home/nilsson/Pike/7.6/src/builtin_functions.c:3689
```Pike 7.6Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/4156problem with redefine "`<<" and "`>>" operation2020-03-01T14:55:29ZPeter Bortasproblem with redefine "`<<" and "`>>" operationImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4156
Reported by Andrew Shirrayev, <andrews@gate.ort.spb.ru>
```
$ pike7.6 -v
Pike v7.6 release 75 Copyright &#9560; 1994-2006 Link&#1046;ping University
Pike comes with ...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4156
Reported by Andrew Shirrayev, <andrews@gate.ort.spb.ru>
```
$ pike7.6 -v
Pike v7.6 release 75 Copyright ╘ 1994-2006 LinkЖping University
Pike comes with ABSOLUTELY NO WARRANTY; This is free software and you are
welcome to redistribute it under certain conditions; Read the files
COPYING and COPYRIGHT in the Pike distribution for more details.
```
Code sample with problem.
```
class test {
object(test) `/(string str)
{
write("DIV : "+str+"\n");
return this_object();
};
object(test) `+(string str)
{
write("ADD : "+str+"\n");
return this_object();
};
object(test) `<<(string str)
{
write("LEFT:"+str+"\n");
return this_object();
};
}
int main(int argc, array argv)
{
object(test) foo=(test()/"qqq")+"zzz";
// ^^ line w/o problem
object(test) foo1=(test()/"qqq")<<"zzz";
// bug.pike:25:Bad argument 2 to `<<.
// bug.pike:25:Expected: !function(!object ... : mixed) & (function(mixed,
// object : mixed) | function(object, mixed : mixed)) | function(int, int :
// int)
// bug.pike:25:Got : function(mixed | void, string : void | mixed)
// Pike: Failed to compile script:
// Compilation failed.
}
```Pike 7.6Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/4059Graphics.Graph.graph() doesn't set legend colors.2022-10-06T09:57:46ZPeter BortasGraphics.Graph.graph() doesn't set legend colors.Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4059
Reference: http://www.siriushosting.com/test.png
Reported by Adam Montague, Sirius Hosting <amontague@siriushosting.com>
When creating a graph with Graphics.Graph.p...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4059
Reference: http://www.siriushosting.com/test.png
Reported by Adam Montague, Sirius Hosting <amontague@siriushosting.com>
When creating a graph with Graphics.Graph.pie() or bar(), if you set
legend_texts to something, then a legend will be created with appropriately
colored boxes. If you do the same with Graphics.Graph.graph(), then the
little boxes in the legend are all white.Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/4049Mutex error2015-03-27T17:42:03ZPeter BortasMutex errorImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4049
Reported by Jonas Wallden <jonasw@roxen.com>
Loading of a Roxen CMS AC dump file triggers the following backtrace (generated with version
4.0.425-release5) where a m...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4049
Reported by Jonas Wallden <jonasw@roxen.com>
Loading of a Roxen CMS AC dump file triggers the following backtrace (generated with version
4.0.425-release5) where a mutex ends up in an odd internal state. The mutex problem occurrs
in the destroy() method in class AC_DB_old::lock in AC.pmod (also in CMS). Grubba made a wild
guess that the destruction of objects instantiated from nested classes may be involved.
The data file that reproduces the error is available upon request since it contains customer data.
```
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912496220160 (LWP 32410)]
exit_mutex_key_obj (o=Variable "o" is not available.
) at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/threads.c:1344
1344 /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/threads.c: No such file or
directory.
in /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/threads.c
(gdb) bt
#0 exit_mutex_key_obj (o=Variable "o" is not available.
) at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/threads.c:1344
#1 0x00000000004932bf in destruct (o=0x10159f0)
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/object.c:728
#2 0x00000000004934e8 in schedule_really_free_object (o=0x10159f0)
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/object.c:873
#3 0x00000000004d2690 in assign_to_short_svalue (u=0x21b8a20, type=3 '\003',
s=0x2aaaaab05360)
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/svalue.c:410
#4 0x000000000042c5bc in eval_instruction (pc=0xf42b2f "K")
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/interpret_functions.h:943
#5 0x000000000042fa78 in mega_apply (type=Variable "type" is not available.
)
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/interpret.c:1774
#6 0x000000000043055f in safe_apply_low2 (o=0x10148e8, fun=3, args=0, handle_errors=1)
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/interpret.c:1939
#7 0x00000000004930f9 in call_destroy (o=0x10148e8, foo=0)
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/object.c:652
#8 0x000000000049319a in destruct (o=0x10148e8)
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/object.c:696
#9 0x0000000000494e39 in low_destruct_objects_to_destruct ()
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/object.c:831
#10 0x0000000000427118 in eval_instruction (pc=0x1fb7949 "|k\005")
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/interpret_functions.h:1414
#11 0x0000000000430242 in o_catch (pc=0x10a49be "&")
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/interpret.c:1818
#12 0x0000000000427f53 in eval_instruction (pc=0x10a49b9 "j\016")
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/interpret_functions.h:1195
#13 0x000000000042fa78 in mega_apply (type=Variable "type" is not available.
)
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/interpret.c:1774
#14 0x000000000045598a in backend_do_call_outs (me=0x821710)
at /home/dist/tmp/build/pike.srcbuild/../pike-cvs/src/backend.cmod:1946
#15 0x0000000000456003 in low_backend_once (me=0x821710, timeout=0x7fffffcfe720)
at /home/dist/tmp/build/pike.srcbuild/../pike-cvs/src/backend.cmod:1434
#16 0x00000000004563d0 in f_Backend_cq__backtick_28_29 (args=-1431285136)
at /home/dist/tmp/build/pike.srcbuild/../pike-cvs/src/backend.cmod:1473
#17 0x0000000000424de3 in low_mega_apply (type=APPLY_SVALUE, args=Variable "args" is not
available.
)
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/apply_low.h:195
#18 0x000000000042b425 in eval_instruction (pc=0x8a46db "µ.P\030Lµ.WõÿÿÿI%NÀM'%
¾¸jöÿÿÿP\030Lµ.P\030Lµ.WØÿÿÿ»")
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/interpret_functions.h:1878
#19 0x0000000000430242 in o_catch (pc=0x8a46d8 "P\030Lµ.P\030Lµ.WõÿÿÿI%NÀM'%
¾¸jöÿÿÿP\030Lµ.P\030Lµ.WØÿÿÿ»")
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/interpret.c:1818
#20 0x0000000000427f53 in eval_instruction (pc=0x8a46d3 "j\023")
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/interpret_functions.h:1195
#21 0x000000000042fa78 in mega_apply (type=Variable "type" is not available.
)
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/interpret.c:1774
#22 0x0000000000489976 in main (argc=11, argv=0x7fffffcfedd8)
at /home/dist/build/4.0/build/pike.fc4_x86_64/pike/src/main.c:756
```Pike 7.4Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/4022Sendfile/call_out attempts to call functions in destructed objects.2009-04-16T14:11:39ZPeter BortasSendfile/call_out attempts to call functions in destructed objects.Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4022
Reported by @grubba
```
From: Eiichiro ITANI <itani@cdjapan.co.jp>
To: Henrik Grubbström <grubba@roxen.com>
Date: Wed, 19 Oct 2005 23:29:53 +0900
Subject: Re: cannot...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4022
Reported by @grubba
```
From: Eiichiro ITANI <itani@cdjapan.co.jp>
To: Henrik Grubbström <grubba@roxen.com>
Date: Wed, 19 Oct 2005 23:29:53 +0900
Subject: Re: cannot call functions in destructed objects?
```
Thank you for your information. I replaced one of our 4.0 server to
pike 7.4.272. It may take a day or so to see infinite loop won't
happen. I still get errors below sometimes, but as far as server
still stands, it's not much problem.
Cannot call functions in destructed objects.
Unknown program: destructed object->function(0)
_static_modules.Builtin()->Backend:
Pike.Backend(0)->`()(_static_modules.files()->sendfile())
This looks like almost same kind of error before...
Anyway, I'll watch our server and will report condition. Still just
an hour and a half, but it looks good.
Thank you for your advice.
--
Eiichiro ITANI <itani@neowing.co.jp> / <itani@cdjapan.co.jp>Pike 7.4Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/4014"Inf" broken2009-11-17T17:46:23ZPeter Bortas"Inf" brokenImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4014
Reported by Anders Johansson <anders@roxen.com>
```
Pike v7.4 release 329 running Hilfe v3.5 (Incremental Pike Frontend)
> 1e71;
(1) Result:
100000000000000004188152...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4014
Reported by Anders Johansson <anders@roxen.com>
```
Pike v7.4 release 329 running Hilfe v3.5 (Incremental Pike Frontend)
> 1e71;
(1) Result:
100000000000000004188152556421145795899143386664033828314342771180699648.000000
> 1e72;
(2) Result:
999999999999999943801810948794571024057224129020550531544123892056457216.000000
> 1e73;
zsh: 19792 segmentation fault ~/Pike/7.4/bin/pike
```Pike 7.4Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/4007Regression in Image.PSD.decode_layers2009-04-16T14:11:39ZPeter BortasRegression in Image.PSD.decode_layersImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4007
Reported by Martin Stjernholm <mast@roxen.com>
Architecture: x86_64
The attached picture gets odd dimensions in 7.6:
```
Pike v7.6 release 37 running Hilfe v3.5 (I...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4007
Reported by Martin Stjernholm <mast@roxen.com>
Architecture: x86_64
The attached picture gets odd dimensions in 7.6:
```
Pike v7.6 release 37 running Hilfe v3.5 (Incremental Pike Frontend)
> Image.PSD.decode_layers(Stdio.read_file("cut.psd"));
(1) Result: ({ /* 1 element */
Image.Layer("normal" i=0 a=Image.Image( 9 x 0 /* 0.0Kb */))
})
```
In 7.4 it works fine:
```
> Image.PSD.decode_layers(Stdio.read_file("cut.psd"));
(1) Result: ({ /* 1 element */
Image.Layer("normal" i=Image.Image( 9 x 13 /* 0.3Kb */)
a=Image.Image( 9 x 13 /* 0.3Kb */))
})
```
A theory is that it's some kind of 64 bit bug.Pike 7.6Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/4000readdir_r/pathconf race condition.2009-04-16T14:11:39ZPeter Bortasreaddir_r/pathconf race condition.Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4000
Reported by Ben Hutchings, <ben@decadentplace.org.uk>
I need to report a potential security bug ahead of public disclosure.
Please can this issue be marked as non-pu...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4000
Reported by Ben Hutchings, <ben@decadentplace.org.uk>
I need to report a potential security bug ahead of public disclosure.
Please can this issue be marked as non-public before I add the details.Pike 7.6Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/3995Syntax error with constant within function gives segmentation fault2009-04-16T14:11:39ZPeter BortasSyntax error with constant within function gives segmentation faultImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3995
Reported by Fredrik Noring, Roxen Internet Software <noring@roxen.com>
foo.pike:
```
int main(int argc, array argv)
{
constant settings = ([
"thumb":([ "small...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3995
Reported by Fredrik Noring, Roxen Internet Software <noring@roxen.com>
foo.pike:
```
int main(int argc, array argv)
{
constant settings = ([
"thumb":([ "small":([ "maxwidth":100,
"maxheight":100
])
]);
]);
return 0;
}
```
gives:
```
$ pike foo.pike
/tmp/foo.pike:7:Missing ']'.
/tmp/foo.pike:7:syntax error, unexpected ';', expecting ')'
/tmp/foo.pike:7:Missing ')'.
Segmenteringsfel
```Pike 7.4Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/3992Protocols.DNS.client() not functional on Windows2022-08-28T23:37:40ZPeter BortasProtocols.DNS.client() not functional on WindowsImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3992
Reported by Anders Johansson <anders@roxen.com>
All syncronous operations with Protocols.DNS.client is broken on windows.
The following program only returns the expe...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3992
Reported by Anders Johansson <anders@roxen.com>
All syncronous operations with Protocols.DNS.client is broken on windows.
The following program only returns the expected result from the second part
when using the async_client (which by the way is undocumented). This was
tested on both Windows 2000 and 2003.
```
void got_result(string from, string to, mixed ... extra)
{
werror("Got result: %O, %O, %O\n", from, to, extra);
}
int main()
{
Protocols.DNS.client con = Protocols.DNS.client();
werror("Host: %O\n", con->gethostbyname("wwww.roxen.com"));
werror("MX: %O\n", con->get_primary_mx("roxen.com"));
werror("Sync: %O\n", con->do_sync_query(con->mkquery("pike.ida.liu.se",
Protocols.DNS.C_IN,
Protocols.DNS.T_A)));
Protocols.DNS.async_client dns = Protocols.DNS.async_client();
dns->host_to_ip("www.roxen.com", got_result);
dns->get_mx("roxen.com", got_result);
return -17;
}
When using Stdio.UDP directly this is the result:
C:\pike\pike\7.4.326\bin>pike
Pike v7.4 release 326 running Hilfe v3.5 (Incremental Pike Frontend)
> object udp = Stdio.UDP();
> string s =Protocols.DNS.protocol()->mkquery("www.roxen.com",
Protocols.DNS.C_IN, Protocols.DNS.T_A);
> udp->bind(0);
(1) Result: Stdio.UDP()
> udp->send("212.247.28.2", 53, s);
(2) Result: 31
> udp->wait(5);
udp->wait(): select() failed with errno 10038
Stdio.UDP: Stdio.UDP()->wait(5)
HilfeInput:1: HilfeInput()->___HilfeWrapper()
```Pike 7.6Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/3950Found uncatched error in Search2009-04-16T14:11:39ZPeter BortasFound uncatched error in SearchImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3950
Reported by Marcus Wellhardh <wellhard@roxen.com>
```
: HTTP Error 302: URI("http://www.ementor.se/")
Standards.URI: got a relative URI (no scheme) lacking a base_ur...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3950
Reported by Marcus Wellhardh <wellhard@roxen.com>
```
: HTTP Error 302: URI("http://www.ementor.se/")
Standards.URI: got a relative URI (no scheme) lacking a base_uri!
/home/wellhard/projects/pike-7.4/lib/modules/Standards.pmod/URI.pike:213:
URI("0:")->reparse_uri(UNDEFINED)
/home/wellhard/projects/pike-7.4/lib/modules/Standards.pmod/URI.pike:312:
URI("0:")->create("/templates/StartPage.aspx?id=2089",UNDEFINED)
/home/wellhard/projects/pike-7.4/lib/modules/Web.pmod/Crawler.pmod:751:
Web.Crawler.Crawler()->HTTPFetcher(302 Found)->got_data()
/home/wellhard/projects/pike-7.4/lib/modules/Protocols.pmod/HTTP.pmod/Query.pike:337:
Web.Crawler.Crawler()->HTTPFetcher(302 Found)->async_fetch_close()
/home/wellhard/projects/pike-7.4/lib/modules/Stdio.pmod/module.pmod:752:
Stdio.File("socket", "62.148.45.238:80", 777 /* fd=-1
*/)->__stdio_read_callback()
_static_modules.Builtin()->Backend: Pike.Backend(0)->`()()
/home/wellhard/projects/pike-7.4/build/linux-2.6.11-1.35_fc3-x86_64/master.pike:2328:
master()->_main(({"/home/wellhard/projects/pike-7.4/build/linux-2.6.11-1.35_fc3-x86_64/pike",,,6}),({"REMOTE_IDENTIFIER=gilch7e","JREHOME=/i/jdk/jdk1.4.1_03/jre","SSH_AGENT_PID=10264",,,49}))
: Exiting due to uncatched error.
```Pike 7.4https://git.lysator.liu.se/pikelang/pike/-/issues/3948GLUT module dependencies fail on Mac OS X.3.92020-03-01T14:50:48ZPeter BortasGLUT module dependencies fail on Mac OS X.3.9Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3948
Reported by Hermann Kruud, <hermannkruud@yahoo.co.uk>
When building Pike v7.7 release 21 (also v7.6 release 24 and v7.4 release
25) on Mac OS X.3.9 the output regard...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3948
Reported by Hermann Kruud, <hermannkruud@yahoo.co.uk>
When building Pike v7.7 release 21 (also v7.6 release 24 and v7.4 release
25) on Mac OS X.3.9 the output regarding the GLUT module is:
configure: configuring in GLUT
configure: running /bin/bash -norc
'/Users/kruud/Sources/Pike/7.7/src/post_modules/GLUT/configure'
--prefix=/usr/local/pike '--prefix=/usr/local/pike' '--with-debug'
'CC=/usr/bin/gcc' 'CFLAGS=-I/sw/include -I/usr/X11R6/include
-I/usr/local/include' 'CPPFLAGS=-I/sw/include -I/usr/X11R6/include
-I/usr/local/include' 'LDFLAGS=-L/sw/lib -L/usr/X11R6/lib -L/usr/local/lib'
'--cache-file=.././config.cache'
'--srcdir=/Users/kruud/Sources/Pike/7.7/src/post_modules'
--cache-file=../.././config.cache
--srcdir=/Users/kruud/Sources/Pike/7.7/src/post_modules/GLUT
configure: loading cache ../.././config.cache
###################################################
## Configuring module: GLUT
## Installation dir:
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... (cached) o
checking whether we are using the GNU C compiler... (cached) yes
checking whether /Users/kruud/Sources/Pike/7.7/bin/smartlink
/usr/bin/gcc accepts -g... (cached) yes
checking for /Users/kruud/Sources/Pike/7.7/bin/smartlink /usr/bin/gcc
option to accept ANSI C... (cached) none needed
checking if we are using TCC (TenDRA C Compiler)... (cached) no
checking how to run the C preprocessor... /usr/bin/gcc -E
checking for X... (cached) libraries /usr/X11R6/lib, headers
/usr/X11R6/include
checking for egrep... (cached) grep -E
checking for ANSI C header files... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for memory.h... (cached) yes
checking for strings.h... (cached) yes
checking for inttypes.h... (cached) yes
checking for stdint.h... (cached) yes
checking for unistd.h... (cached) yes
checking for gnu/stubs.h... (cached) no
checking for gethostbyname... (cached) yes
checking for connect... (cached) yes
checking for remove... (cached) yes
checking for shmat... (cached) yes
checking for IceConnectionNumber in -lICE... (cached) yes
X_CFLAGS: -I/usr/X11R6/include
X_LIBS: -L/usr/X11R6/lib
X_EXTRA_LIBS:
X_PRE_LIBS: -lSM -lICE
checking GL/glut.h usability... yes
checking GL/glut.h presence... yes
checking for GL/glut.h... yes
checking GLUT/glut.h usability... yes
checking GLUT/glut.h presence... yes
checking for GLUT/glut.h... yes
checking for XDrawPoint in -lX11... yes
checking for XShmPutImage in -lXext... yes
checking for XmuStandardColormap in -lXmu... yes
checking for glOrtho in -lGL... yes
checking for glOrtho in -lOpenGL... no
checking for glOrtho in -lMesaGL... no
checking for gluCylinder in -lGLU... yes
checking for gluCylinder in -lMesaGLU... no
checking for XOpenDevice in -lXinput... no
checking for XOpenDevice in -lXi... yes
checking for glutSolidTeapot in -lglut... no
checking for glutSolidTeapot in GLUT.framework... no
checking for glutEnterGameMode... no
checking for glutForceJoystickFunc... no
checking for glutGameModeGet... no
checking for glutGameModeString... no
checking for glutIgnoreKeyRepeat... no
checking for glutInitDisplayString... no
checking for glutJoystickFunc... no
checking for glutKeyboardUpFunc... no
checking for glutLeaveGameMode... no
checking for glutPostWindowOverlayRedisplay... no
checking for glutPostWindowRedisplay... no
checking for glutReportErrors... no
checking for glutSetKeyRepeat... no
checking for glutSpecialUpFunc... no
checking whether make sets $(MAKE)... (cached) yes
checking for the Pike base directory... /Users/kruud/Sources/Pike/7.7/src
updating cache ../.././config.cache
configure: creating ./config.status
config.status: creating make_variables
config.status: creating Makefile
config.status: creating config.h
config.status: executing default commands
Eventually the GLUT module doesn't compile:
GLUT................ no (dependencies failed)Pike 7.8Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/3944glibc crash2011-02-08T16:05:06ZPeter Bortasglibc crashImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3944
Reported by Thomas Bopp, Uni-GH Paderborn <astra@upb.de>
*** glibc detected *** free(): invalid next size (fast): 0x600000001021f780 ***
Does this happen inside the...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3944
Reported by Thomas Bopp, Uni-GH Paderborn <astra@upb.de>
*** glibc detected *** free(): invalid next size (fast): 0x600000001021f780 ***
Does this happen inside the GC ? This is the second or third crash after uptime of 1-2 weeks.
Pike Version is 7.4.44.Pike 7.4Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/3943Crash with error: "Illegal shift size" in stralloc.c2009-04-16T14:11:39ZPeter BortasCrash with error: "Illegal shift size" in stralloc.cImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3943
Reported by Robert Hinn, University of Paderborn <exodusd@gmx.de>
```
/root/Pike/7.4/src/stralloc.c:151: Fatal error:
Illegal shift size!
Backtrace at time of fatal:...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3943
Reported by Robert Hinn, University of Paderborn <exodusd@gmx.de>
```
/root/Pike/7.4/src/stralloc.c:151: Fatal error:
Illegal shift size!
Backtrace at time of fatal:
operators.c:3823: object(src/operators.c:3823)->`[]=(101,49)
tmp/modules/tar.pike:76:
object(/usr/local/lib/steam/tmp/modules/tar.pike)->buffer_copy("0100664",100)
tmp/modules/tar.pike:121:
object(/usr/local/lib/steam/tmp/modules/tar.pike)->tar_header("stylesheets/",UNDEFINED)
```
on another server it seems to work (7.4.21)
there is also a coredump...Pike 7.4Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/3942Postgres information outdated/inaccurate (patch included)2011-02-09T14:21:46ZPeter BortasPostgres information outdated/inaccurate (patch included)Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3942
Reported by Adam Montague, Sirius Hosting <amontague@siriushosting.com>
This patch fixes the following issues with the postgres info:
postgresql is not particularly ...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3942
Reported by Adam Montague, Sirius Hosting <amontague@siriushosting.com>
This patch fixes the following issues with the postgres info:
postgresql is not particularly slow
username and password are not ignored when connecting
you always have a db selected with postgres, so you don't have to worry
about it throwing exceptions if you didn't select a db
and the environment variable information has been updatedPike 7.6Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/3941configure script's dynamic linking check fails on openbsd2009-04-16T14:11:39ZPeter Bortasconfigure script's dynamic linking check fails on openbsdImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3941
Reported by Adam Montague, Sirius Hosting <amontague@siriushosting.com>
```
The LDSHARED setting for openbsd should look like:
OpenBSD*) LDSHARED="$REALCC -Wl,-Bshar...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3941
Reported by Adam Montague, Sirius Hosting <amontague@siriushosting.com>
```
The LDSHARED setting for openbsd should look like:
OpenBSD*) LDSHARED="$REALCC -Wl,-Bshareable";;
instead of :
OpenBSD*) LDSHARED="ld -Bshareable";;
and LINKFORSHARED needs to look like:
OpenBSD*) LINKFORSHARED="-Wl,-E";;
```
Dynamic modules work fine after those changes are made.Pike 7.6Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbströmhttps://git.lysator.liu.se/pikelang/pike/-/issues/3935Filesystem.Traversion doesn't check if directory listing succeeded2022-08-28T19:40:46ZPeter BortasFilesystem.Traversion doesn't check if directory listing succeededImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3935
Reported by Adam Montague, Sirius Hosting <amontague@siriushosting.com>
If you create a Filesystem.Traversion object for a directory that contains
a directory that y...Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3935
Reported by Adam Montague, Sirius Hosting <amontague@siriushosting.com>
If you create a Filesystem.Traversion object for a directory that contains
a directory that you do not have permissions to list (execute), then you
get a non-obvious and lengthy error message. I think its assuming that
listing of directories succeeds, instead of either skipping directories
with no permission to list, or throwing an exception. Here's the error I
get if I foreach a Filesystem.Travsion(".") object when I don't have
permission to list the ./models directory:
```
Bad argument 1 to sizeof().
/usr/local/lib/pike/modules/Filesystem.pmod/module.pmod:287:
/${PIKE_MODULE_PATH}/Filesystem.pmod/module.Traversion()->create("./
models",0)
/usr/local/lib/pike/modules/Filesystem.pmod/module.pmod:226:
/${PIKE_MODULE_PATH}/Filesystem.pmod/module->Traversion()
/usr/local/lib/pike/modules/Filesystem.pmod/module.pmod:301:
/${PIKE_MODULE_PATH}/Filesystem.pmod/module.Traversion()->set_current()
/usr/local/lib/pike/modules/Filesystem.pmod/module.pmod:324:
/${PIKE_MODULE_PATH}/Filesystem.pmod/module.Traversion()->add(1)
/usr/local/lib/pike/modules/Filesystem.pmod/module.pmod:329:
/${PIKE_MODULE_PATH}/Filesystem.pmod/module.Traversion()->`+=(1)
```Pike 7.8https://git.lysator.liu.se/pikelang/pike/-/issues/3933Roxen self test module ... OK: 16440 Bus Error - core dumped2009-04-16T14:11:39ZPeter BortasRoxen self test module ... OK: 16440 Bus Error - core dumpedImported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3933
Reported by Fredrik Noring, Roxen Internet Software <noring@roxen.com>
Self test terminates with "Bus Error" on Solaris 8 Sparc:
/home/dist/tmp/self-test/roxen-4.0....Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=3933
Reported by Fredrik Noring, Roxen Internet Software <noring@roxen.com>
Self test terminates with "Bus Error" on Solaris 8 Sparc:
/home/dist/tmp/self-test/roxen-4.0.351-test-cms-sol8_sparc.sh:
Enabling all modules for Test Platform...
Roxen self test module ... OK 3.1ms
16440 Bus Error - core dumped
Start script terminating.
Shutting down MySQL..
Start script terminated.
Dist self test done.Pike 7.4Henrik (Grubba) GrubbströmHenrik (Grubba) Grubbström