Hi,
I'm speech recognition researcher not so fond of newer Linux systems. I have some old ansi C code that I used to run under Debian 2.0.
Now I transferred code to Suse 9.0, compile it without any errors (some warnings) but get segmentation faults in runtime.
One particular error is (I get this when run in ddd):
Program received signal SIGSEGV, Segmentation fault. 0x400b90af in fflush() from /lib/libc.so.6
---------------- My C knowledge is rusty (I checked up this code long time ago) so I'd kindly ask for some quick guidance, how to deal with such segfaults. If I remember right there were some tools that could help in debugging memory accesses(efence or something like that) - I guess tools are now much more advanced - but I don't know which one to use... As Adalberto mentions, valgrind is a good tool, especially for memory leaks. Segmentation faults in system libraries is usually a result of some prior memory allocation issue, such as addressing beyond the end of allocated memory or simply a bad pointer, in this case possibly to a FILE structure. Another (but expensive) tool is Rational's Purify. I recommended that to someone else who supplies an API where the customer was complaining about a memory leak. After several weeks of using other tools, he used Purify, which found the problem in 5 minutes. They were so impressed,
On Mon, 20 Sep 2004 22:43:58 +0200
"Robert Rozman"