Re: segfault on kernel v2.4.0

[Chris Kuklewicz <chrisk@mit.edu>]

Again, I am not a developer on this project.  But I do have more ideas
on collecting data:

> modprobe loop
> losetup
> => segfault

If you use strace, e.g. "strace losetup ...", does the output help you
isolate an offending syscall?  Note: strace is pretty easy to use, see
the man page.

If you compare the strace output with output where you preloaded
blowfish and avoided the segfault, then it might help locate a failing
syscall, if there is one.

Or try running gdb on losetup (perhaps also recompile losetup with -g
for debugging).  Note: you need to know some gdb (or front end to gdb)
to do this.  This isolates other errors, such as dereferencing null
pointers and dividing by zero.

Again, using gdb to compare where losetup failed with the case where
blowfish is preloaded may help.

-- 
Chris

Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/