Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

mktestsuite and m4
by william＠welliver.org 25 Jan '22

25 Jan '22

I've traced down some problems running the testsuite on systems that ship with a non-gnu m4. Specifically, mktestsuite calls m4 with the "-d" argument. Using gm4, the lack of flags implies the a,e and q flags. On BSD m4, the "-d" argument /requires/ flags, though the flags themselves are the same as GNU m4. POSIX/Solaris/illumos m4 doesn't support the debug argument at all. Looking at mktestsuite, it tries to determine whether it's using GNU m4, and will prefer (but not require it) it should it find one. Once it's chosen the m4 binary, it seems to assume that GNU options are acceptable. Since that doesn't work, I'm wondering what the preferred ought to be: 1. require GNU m4 2. just use the full -d argument and hope (solaris/etc) users will figure out they need gm4 3. try to detect what sub-flavor of non-GNU m4 is being used I don't recall the last time I ran across a solaris system without the gnu build tools. I'd be inclined to take option 2 since it shouldn't break anyone and will improve the situation for some. A more elaborate solution could be considered if some POSIX purists complain later. Thoughts? Bill

2 1

pike-stable 7.8/SSL test failures
by william＠welliver.org 15 Jan '22

15 Jan '22

Hello all- I've been looking at some test failures in the stable tree (I haven't looked at whether they're present in the development tree yet) occurring in the 7.8/SSL testsuite. The failures happen on netbsd and illumos at a minimum, and I'm not able to see what's actually wrong, as the a/b values are equal. Examples can be found in this verifylog.txt: https://paste.sr.ht/~hww3/6fca76d6c19743525e0b1f7325fea4213b100ecd#http://p… The original file is: http://pike.lysator.liu.se/generated/pikefarm/results/8.0/6652_154/verifylo… So, if o->a==o->b, then why is the test failing? These are not new failures, but if there's a simple solution, I'd like to fix them. Any thoughts? Bill

3 2

Pike debugger update
by H William Welliver 23 Dec '21

23 Dec '21

Hello all- I’ve got a little free time on my hands again and am planning on spending a bit of time working on the pike debugger prototype. My first effort will be to merge the existing support into the development branch so that it gets a little more exposure. I plan on doing this as a series of commits: the C-level changes, the low-level Pike code and finally the Debug Adapter Protocol support. I don’t expect this to cause any problems for people not using the debugger, but hopefully merging it will make it a lower effort to test. There should be a more complete message about this proposal (and I didn’t get any pushback) so assume it’s still okay to proceed. Please do get in touch if there are any reservations. The second effort that I’d like to tackle is figuring out a way to perform code evaluation at a particular stack frame. I think this is the major missing “base function” that’s currently missing. I’d be pleased to hear any suggestions you might have for how best to accomplish this. I was thinking that the hilfe code might provide a way, with global/local variable resolution via the live stack frame object that the debugger will have access to. Is there possibly a better way? Bill

1 0

New Pike stable release
by H William Welliver 23 Dec '21

23 Dec '21

Hello all- After a bit of a delay, I’m getting ready to cut a new 8.0 release candidate. If anyone still has any remaining commits bound for 8.0, let me know they’re coming (I know it’s a busy time of year, so a quick note is all I’d need right now). If I don’t hear anything by Sunday 1200UTC, I’ll start working on the release. Any comments or questions are welcome! Many thanks for everyone’s contribution this year and I hope you have a wonderful festive season! Bill

1 0

Redis protocol
by Ignasi Cavero 06 Dec '21

06 Dec '21

Hello, I've written a Pike module that implements the Redis protocol (https://redis.io) Licensed under LGPLv3, but if you need another license, please contact me. https://glog.org/Pike/Redis.tar.gz -- *Ignasi Cavero* Técnico de I+D+i | R&D Technician ignasi(a)lleida.net (+34) 652 813 884 *Parc Científic i Tecnològic Agroalimentari de Lleida* Edifici H1 2a planta B | 25003 Lleida (Spain) Tel. 902 999 272 | (+34) 973 282 300 Fax (+34) 973 282 195 www.lleida.net <http://www.lleida.net> Política de privacidad <http://www.lleida.net/es/privacy.html>

1 0

Bug in ccm glue?
by Niels M�ller (entering a radioactive zone) ＠ Pike (-) developers forum 03 Dec '21

03 Dec '21

Hi, I've received a bug report (from someone at Opera) about a crash when using Crypto.AES.CCM. Example int main() { mixed state1 = Crypto.AES.CCM.State(); state1->set_encrypt_key(String.hex2string("bedcfb5a011ebc84600fcb296c15af0d")); state1->set_iv(String.hex2string("438a547a94ea88dce46c6c85")); state1->update(String.hex2string("")); string ct = state1->crypt(String.hex2string("")); state1->digest(); return 0; } When I try it (with Pike v8.0, installed as a debian package on x86_64) it segfaults in nettle_memxor3. As far as I can tell from 5 minutes of printf debugging, crash is inside the call to ->digest(). The set_iv method looks a bit suspicious to me, it doesn't include the required arguments for the nettle function ccm_set_nonce (and ccm is generally a bit messier to setup than most other modes). See http://www.lysator.liu.se/~nisse/nettle/nettle.html#index-ccm_005fset_005fn… There may of course be some problem in the nettle library too, in particular, I would be happier if api misuse resulted in an assert failure rather than a segfault.

2 3

Re: bufferdAmount or bufferedAmount?
by Chris Angelico 19 Nov '21

19 Nov '21

On Fri, Nov 19, 2021 at 10:33 AM ceder (-) Per Cederqvist @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > This code in lib/modules/Protocols.pmod/WebSocket.pmod seems to be > missing an "e": > > //! @decl int bufferedAmount > //! Number of bytes in the send buffer. > > int `bufferdAmount() { > return sizeof(out); > } > > I guess it should be "bufferedAmount", not "bufferdAmount"? Yep, I'd agree. It's entirely possible there's code in the wild depending on the misspelled version though. Might be worth adding the correct one and leaving the existing one as a deprecated alias for it. ChrisA

1 0

bufferdAmount or bufferedAmount?
by ceder (-) Per Cederqvist ＠ Pike (-) developers forum 19 Nov '21

19 Nov '21

This code in lib/modules/Protocols.pmod/WebSocket.pmod seems to be missing an "e": //! @decl int bufferedAmount //! Number of bytes in the send buffer. int `bufferdAmount() { return sizeof(out); } I guess it should be "bufferedAmount", not "bufferdAmount"?

1 0

compile of pike under chroot failing
by cheese＠nosuchhost.net 11 Nov '21

11 Nov '21

hi i'm currently building rpms of pike 8.0 for fedora35 and have troubles to "install" the binaries. my setup: mock (chroot environment for building rpms). inside of that environment there are several steps, mainly extract source-files, prepare, compile, install and collect the final binaries. the install step for both x86_64 and aarch64 seems to stop at: Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.bdeWDr + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 ++ dirname /builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 + cd Pike-v8.0.1116 + buildroot=/builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 + rm -rf /builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 + cd build + /usr/bin/make buildroot=/builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64 install 'INSTALLARGS=buildroot='\''/builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64'\'' lib_prefix='\''/usr/lib64/pike80'\'' include_prefix='\''/usr/include/pike80'\'' --traditional' Makefile:478: warning: ignoring prerequisites on suffix rule definition Makefile:524: warning: ignoring prerequisites on suffix rule definition make[1]: Entering directory '/builddir/build/BUILD/Pike-v8.0.1116/build' Makefile:478: warning: ignoring prerequisites on suffix rule definition Makefile:524: warning: ignoring prerequisites on suffix rule definition make[1]: Leaving directory '/builddir/build/BUILD/Pike-v8.0.1116/build' make[1]: Entering directory '/builddir/build/BUILD/Pike-v8.0.1116/build' Makefile:478: warning: ignoring prerequisites on suffix rule definition Makefile:524: warning: ignoring prerequisites on suffix rule definition make[1]: Leaving directory '/builddir/build/BUILD/Pike-v8.0.1116/build' Installing Pike in /builddir/build/BUILDROOT/pike80-8.0.1116-1.fc35.aarch64/usr, please wait... i'm waiting for several hours (around 16) now attaching with strace to the running pike gets me: close_range(11, -1, 0) = -1 EPERM (Operation not permitted) openat(AT_FDCWD, "/proc/self/fd/", O_RDONLY|O_DIRECTORY) = 9 getdents64(9, 0x7ffdc355bb80 /* 13 entries */, 1024) = 312 getdents64(9, 0x7ffdc355bb80 /* 0 entries */, 1024) = 0 close(9) = 0 close_range(11, -1, 0) = -1 EPERM (Operation not permitted) openat(AT_FDCWD, "/proc/self/fd/", O_RDONLY|O_DIRECTORY) = 9 getdents64(9, 0x7ffdc355bb80 /* 13 entries */, 1024) = 312 getdents64(9, 0x7ffdc355bb80 /* 0 entries */, 1024) = 0 close(9) .... fast looping over that lines any ideas? the same under fedora 34 built correctly. any suggestions? yours josef

3 4

mailling list archive not complete
by cheese＠nosuchhost.net 10 Nov '21

10 Nov '21

hi i see some mails in my inbox from pike-devel which are missing in the online archive at http://lists.lysator.liu.se/pipermail/pike-devel/2021-October/date.html eg. the answers for "New Pike 8.0 release?" from william are missing online. yours josef

1 0

← Newer
1
2
3
4
5
6
7
8
...
305
Older →

Jump to page:

2025

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