bogoutil segfaults

[David Relson]

Clint & Matthias,

Below I've trimmed the output a bit, so all that's left is the bogoutil 
invocation and the dump_file().

At 08:35 AM 7/23/03, Clint Adams wrote:

>Core was generated by `../../bogoutil -a 20020815 -s4,30 -d 
>./checks.1487.20030723T083159/t.dump.load.'.
>Program terminated with signal 11, Segmentation fault.
...[snip]...
>#2  0x0001179c in dump_file (db_file=0x1317e4f <Address 0x1317e4f out of 
>bounds>) at ../../bogofilter-0.14.0/src/bogoutil.c:178


>Core was generated by `../../bogoutil -d 
>./checks.1567.20030723T083209/wordlist.db'.
>Program terminated with signal 11, Segmentation fault.
...[snip]...
>#2  0x0001179c in dump_file (db_file=0x131a35f <Address 0x131a35f out of 
>bounds>) at ../../bogofilter-0.14.0/src/bogoutil.c:178

It's very strange that the first parameter to dump_file() is bad.

Here's the code that sets and uses that parameter:

         case 'd':
             flag = DUMP;
             count += 1;
             db_file = (char *) optarg;

         case DUMP:
             return dump_file(db_file);

Of course, _this_ portion of bogoutil has not changed.

Guess I'll have to stare at the code awhile to see what ideas pop-up.  Have 
either of you any thoughts on this?