need help debugging nessus
"Gene C." <[email protected]>
| Newsgroups | gmane.comp.security.nessus.devel |
|---|---|
| Message-ID | <[email protected]> |
I am trying to get nessus working as a 64 bit application on (Fedora Core ) linux. I have the lib64 patches from SUSE. I also have gcc fixed so that it does not loop when compiling network.c. I have also found at least one other bug where nessus is using the "wrong" struc ... and will pass the patches upstream once I get more accomplished. I have found a number of seg-faults (SIGSEGV) in nmap_tcp_connect.nes as well as possibles in some NASL scripts (although they run fine with the nasl command so it may be something else). Since nessus makes extensive use of fork-process, I am having difficulty trying to debug things ... ddd seems to be having other problems so I have fallen back to using gdb. However, when I run gdb by attaching the "nessusd serving" process, the tests are not run. Any hints on how to use gdb with nessus? Many times when debugging, I insert printf or fprintf statements into the source code so that I can print out info to help see what is going on. I have having difficulty getting anything. Is there something I can use to get info into the logs/nessusd.dump or logs/nessusd.message files? I tried "log_write" but that does not seem to work. Any hints appreciated. -- Gene _______________________________________________ Nessus-devel mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus-devel