The problem is an array out of bounds. Because this yields undefined behaviour, some versions of gcc cause a segfault, others simply copy bogus memory to a structure field that will never be read. Other versions might do something else.
Applies to --eamt --display, --pool4 --display, --bib --display and --session --display.
This is an userspace application problem, which means it doesn't crash the kernel.
Thanks to Edgar Rodriguez for pointing this out.
Added code to avoid the index out of bounds. These instructions were …
…meaningless in these situations anyway.
Fixes issue #150.