Could you do another run with gdb, but after the SEGV, type 'bt' into gdb, to show the stack trace. This should indicate where the program is failing. When you copied my version over the original source, did you do a full make clean/configure/make/make install again? Cheers, Mat ----- Original Message ----- From: "Richard Hewitt" <richard.hewitt@one-ten.com> To: <nntpcache-users@suburbia.net> Cc: "'Mat Williamson'" <mat@spam69.demon.co.uk> Sent: Friday, September 01, 2000 11:07 AM Subject: NNTPC: NNTP authorisation + newshound > > Many thanks for that, but it didn't work alas. > > I am not by any means a C programmer, but I've got the conceptuals of how it > works. > So I put newshound (both the one you sent me and the old one) into gdb like > so: > > > [root@phoenix newshound]# gdb newshound > > This GDB was configured as "i386-redhat-linux"... > (gdb) run -d 1 -c > Starting program: /root/nntpcache-2.3.3/contrib/newshound/newshound -d 1 -c > Collecting newsgroups. > File :- /usr/local/var/nntpcache/hound.rf has 0 lines. > Sorting array. > > Program received signal SIGSEGV, Segmentation fault. > strcpy (dest=0xbffffa10 "158.152.254.67/alt/binaries/screen-savers/63488\n", > src=0x0) at ../sysdeps/generic/strcpy.c:37 > 37 ../sysdeps/generic/strcpy.c: No such file or directory. > (gdb) > > > Well, I cant find a file called strcpy.c on my system, or either of the > directories it references. > Greping for it in the newshound source reveals nowt (apart from the numbers of > strcpy function calls dotted about. > I guess it's a problem with my libraries/library path/something similar? > > Any suggestions? > > Many thanks, > > Richard. > > > > -----Original Message----- > > From: Mat Williamson [mailto:mat@spam69.demon.co.uk] > > Sent: 01 September 2000 1:48 > > To: nntpcache-users@suburbia.net > > Cc: Richard Hewitt > > Subject: Re: NNTPC: NNTP authorisation + newshound > > > > > > I had the same problem with newshound on redhat 6.2 causing > > segmentation > > faults. It turned out that the program was trying to close > > files which were > > not actually open, which my version of Linux did not like. > > > > I did some work on the code and fixed this problem then went > > on to add some > > additional code to deal with error conditions a bit better > > plus various > > other stuff, mostly geared to running newshound on dialup > > connections which > > drop unexpectedly. The attached tarball contains my version > > of the source > > code and the contents should be extracted into the contrib > > directory of the > > nntpcache source. Compile this and install and your SEGV > > problem should be > > fixed. > > > > Hope this helps. > > > > Regards, > > Mat. > > > > ----- Original Message ----- > > From: "Richard Hewitt" <richard.hewitt@one-ten.com> > > To: <nntpcache-users@suburbia.net> > > Sent: Thursday, August 31, 2000 11:14 AM > > Subject: NNTPC: NNTP authorisation + newshound > > > > > > > > > > I've read the FAQ and searched the net but couldn't find > > the answers to > > the > > > questions below - can anyone help me? > > > > > > 1) I want to set up nntpcache so that clients have to enter > > username/password > > > to be able to access the cache server. > > > In the nntpcache.access file it says that the AUTHINFO code has been > > > disabled - is there any other way to force > > username/password validation or > > is > > > the only way to control access via IP address? > > > > > > 2) I am trying to use the contributed app newshound. > > nntpcache works fine > > for > > > pulling down messages, but when I try to run newshound as > > per the README > > file > > > for the first time it says > > > > > > File :- /usr/local/var/nntpcache/hound.rf has 0 lines. > > > Sorting array. > > > Seg fault core dumped. > > > > > > > > > /usr/local/var/nntpcache/hound.rf > > > and > > > /usr/local/var/nntpcache/hound.sf both exist but are zero bytes. > > > > > > Any ideas as to what I'm doing wrong? > > > > > > > > > OS Redhat Linux 6.2 > > > nntpcache ver 2.2.3 > > > Newshound ver 2.0 > > > > > > > > > Many thanks in advance, > > > > > > Richard Hewitt > > > > > > > > > > > > >
