|
From: Thomas O. <T.O...@we...> - 2005-11-23 16:12:28
|
Hi, I am working on an extension for the ns2 network simulator, but a Segmentation fault occurs and I was not able to find out why that happened. Then somebody recommented valgrind to me. So I tried it and got a lot of errors not leading to a Segmentation fault. The program runs till the end (needs quite some time, which is meanted on the valgrind Manual). So now I cannot figure out, how to resolve my problem. It is good to see that it seems to work, when i run it with valgrind, but why? Has anybody a clue? Any other suggestions how to resolve a Segmentation fault thats out of the ordinary? ;) Thanks in advance Thomas ______________________________________________________________________ XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club! Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130 |
|
From: John R.
|
> Any other suggestions how to resolve a Segmentation fault thats out of the ordinary? Use 'strace' to see if it is a system call that generates the SIGSEGV. It is tedious to write the code to "wrap" all system calls, and the kernel documentation isn't always helpful; so a pointer argument to a system call might slip by valgrind. [If so, then file a bug report so that the valgrind wrapper can be improved.] -- |
|
From: Jeroen N. W. <jn...@xs...> - 2005-11-23 16:27:14
|
On Wed, November 23, 2005, Thomas Ogilvie wrote: > > Hi, > > I am working on an extension for the ns2 network simulator, but a > Segmentation fault occurs and I was not able to find out why that > happened. Then somebody recommented valgrind to me. So I tried it and got > a lot of errors not leading to a Segmentation fault. The way to proceed is to fix the problems that Valgrind did find. Even if they do not lead to a SEGFAULT, they *are* errors. The difference in behavior can be the result of, for instance, an uninitialized variable having different values with or without Valgrind. Jeroen. > The program runs till > the end (needs quite some time, which is meanted on the valgrind Manual). > So now I cannot figure out, how to resolve my problem. It is good to see > that it seems to work, when i run it with valgrind, but why? Has anybody a > clue? Any other suggestions how to resolve a Segmentation fault thats out > of the ordinary? ;) > > Thanks in advance > > Thomas > ______________________________________________________________________ > XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club! > Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130 > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |
|
From: Julian S. <js...@ac...> - 2005-11-23 16:29:11
|
> I am working on an extension for the ns2 network simulator, but a > Segmentation fault occurs and I was not able to find out why that happened. > Then somebody recommented valgrind to me. So I tried it and got a lot of > errors not leading to a Segmentation fault. The program runs till the end > (needs quite some time, which is meanted on the valgrind Manual). So now I > cannot figure out, how to resolve my problem. You should fix all the errors that valgrind reports. Why do you think they are not related to your segmentation fault? J |