Re: Segmentation Fault with IUP on chicken 5.2.0
On Thu, Feb 25, 2021 at 05:04:14PM -0700, Jeff Moon wrote: > Any ideas what could be causing this, or what I could do to track > it down? Hi Jeff, This sounds like there might be a bug at the toplevel of IUP, which might explain why re-importing works (it shouldn't re-evaluate the toplevel). There are a few things you can do. I would first simply run the program under gdb and see if you can track down in which file and which C function it crashes. Then, see which function this corresponds to in the Scheme code. You will need to compile IUP with the -k option to keep the generated C sources (try CSC_OPTIONS=-k on the chicken-install command line). If that doesn't give you anything useful, you can try using a debugbuild of CHICKEN. This includes many extra runtime safety checks which may cause an earlier crash via an assertion fail. These checks are done at the generated C level as well, so again you'll need to compile IUP and anything related with -k. To get a debugbuild, recompile CHICKEN itself with DEBUGBUILD=1, install it somewhere else and then build IUP and your program, then run it. If it causes an assertion trigger it will crash with some message like this: [panic] Low-level type assertion C_blockp((C_word)C_VAL1(C__PREV_TMPST.n1))=#t failed at library.c:48051 - execution terminated. If this is still not useful enough, try running the program under gdb and put a breakpoint on "usual_panic", then run it again. This will give you a stack trace, so hopefully you can tell by the flow of calls where the program crashed. Cheers, Peter signature.asc Description: PGP signature
Re: Orphan SRFI eggs and maintainership changes
srfis 27, 45, 111 & 195 (tbd)
Re: Orphan SRFI eggs and maintainership changes
> I'm appealing to anyone who has the inclination and time to take over some of > these. I'd like to maintain the following (with new urls following egg names, passed test-new-egg): * srfi-143: https://code.dieggsy.com/srfi-143/plain/srfi-143.release-info * srfi-160: https://code.dieggsy.com/srfi-160/plain/srfi-160.release-info * srfi-197: https://code.dieggsy.com/srfi-197/plain/srfi-197.release-info - Diego
Orphan SRFI eggs and maintainership changes
Hi all, I've been in touch with Sergey Goldgaber, who created a number of eggs for various SRFIs late last year. He's no longer maintaining these eggs: > Sorry, I have been pulled away from the chicken world for the foreseeable > future. The maintainership of these eggs is open for the taking. Feel > free to do what you think best. > > --Sergey There are 25 eggs listed on Sergey's wiki page: https://wiki.call-cc.org/users/sergey-goldgaber I'm appealing to anyone who has the inclination and time to take over some of these. I'd like to take over maintainership for the following eggs. Each egg name is followed by the updated release-info URL: * srfi-78 https://raw.githubusercontent.com/Zipheir/srfi-78/main/release-info * srfi-130 https://raw.githubusercontent.com/Zipheir/srfi-130/main/release-info * srfi-152 https://raw.githubusercontent.com/Zipheir/srfi-152/main/release-info * srfi-196 https://raw.githubusercontent.com/Zipheir/srfi-196-chicken/main/release-info * srfi-207 https://raw.githubusercontent.com/Zipheir/srfi-207-chicken/main/release-info Best regards, -- Wolfgang Corcoran-Mathe "The Algol compiler was so poorly implemented that we dared not rely on it, and working with assembler code was considered dishonorable. There remained only Fortran." --Niklaus Wirth
Segmentation Fault with IUP on chicken 5.2.0
I am having some problems with segmentation faults under chicken. I am running on SLES12 using chicken 5.2.0. I have installed the iup egg version 1.9.5. I have installed iup version 3.30 as well. Whenever I do (import iup), I get a segmentation fault. If I use csi, the first time I import I get a segmentation fault, but if I try to import it again it seems to succeed and then I can make windows and buttons just fine. I made a test script that does a handle-exceptions around the first import, and using that I can compile executables that work OK as well. Any ideas what could be causing this, or what I could do to track it down? Here's my sample script: (import simple-exceptions) (handle-exceptions exn (print "Exception found") (import iup)) (import iup) (show (dialog (label "Hello, world!"))) (main-loop) (exit 0)
