Re: [Chicken-hackers] [PATCH] mutex-lock! sometimes not srfi-18 compliant

Use git commit --amend to fix if you haven't committed the second one yet. Use git rebase -i to squash existing commits together. > On Nov 23, 2015, at 13:45, Jörg F. Wittenberger > wrote: > > Sorry, > > this patch needs a patch. > > Looks like I shot myself

[Chicken-hackers] How to interpret chicken post mortem?

Hi all, just managed to switch to the master branch, eventually. (Congrats to myself, sight ;-) Now there is a segfault. Looks almost random. The program runs for a fairly long time until crash. (Megabytes of chicken -:r backtrace and no hint either). Some gdb backtraces from a debug build