Segmentation fault due to .hiawatha file

7 January 2011, 03:48
Hi Hugo,

It's been a long time

Hiawatha crashes with a segfault after pointing to a directory with a .hiawatha file containing:


Whether this command is incorrect or not; Is this normal behavior?

Hiawatha version: Latest
Operating System: Fortress Linux
Hugo Leisink
7 January 2011, 08:57
ShowIndex seems to work fine here. Please follow these instructions.
7 January 2011, 16:03
Ok, you could not reproduce it. In that case:

- HW configure options used: --enable chroot --prefix=/usr

- I think you could better adjust that valgrind instruction to:
valgrind --tool=memcheck --leak-check=full ./(location-to)/hiawatha -c /(location-to-config-file) -d 2> /var/log/valgrind.txt

The logfile can be found here:
Hugo Leisink
7 January 2011, 22:33
Thanks for your bug report. I'll take a look at it.
Hugo Leisink
7 January 2011, 23:34
Can you please download and try this 7.5 beta [] tarball? Maybe it's something I already fixed.

The provided file is NOT an official release. So please, do not distribute that file.
8 January 2011, 01:30
Sure, you can remove the tarball by now (if you want).

First of all; Before this (In version 7.3) I had a system website-wide "500 internal server error" after after pointing to a directory with a "invalid" .hiawatha file. The only way to solve this, was restarting Hiawatha. I don't know exactly what I put into that file. I think it had something to do with IP blocking rules in Apache style.

Anyway, thank you for the file. It's now running on (yes, it a beta, but it is also secured by an LXC container.)

First time I received an 500 error and the second time it crashed again. Do you need an other report?
Hugo Leisink
8 January 2011, 09:55
More information is always welcome.
9 January 2011, 00:39
I'll will create another report next monday.
11 January 2011, 16:12
Hugo Leisink
11 January 2011, 16:50
Weird... Does this also happen if you place the "ShowIndex = yes" in the main configuration file hiawatha.conf?
13 January 2011, 01:29
and... the same problem. It may have something to do with xml or libc if it works fine with you. I'll upgrade the server as soon as the first Alpha of Fortress Linux is finished this month. I'm now too busy writing an automatic compile/kernel configurator.
Hugo Leisink
13 January 2011, 07:38
Could it be some sort of kernel security patch that is causing the problem?
17 January 2011, 00:50
No, had it tested on a clean Xen kernel w/o grsecurity, SELinux, Pax and not even with with stack_smashing protection at home. (stage 1 test).
Hugo Leisink
17 January 2011, 09:48
Do you have a VMware image available of your Fortress Linux? I can't reproduce the crash on my system. Maybe it's something in Fortress Linux that triggers it.
This topic has been closed.