|
From: Alan S. <new...@gm...> - 2008-02-26 06:42:45
|
My Linux distribution is ST Linux: http://www.stlinux.com/, does anyone compile and run the latest Valgrind on it? Our applications are running on this platform, during the development process, the memory leak and stack over write is very frequency. So I want to use Valgrind on this environment, does anyone use this before? Thanks! BR Alan |
|
From: Dan K. <da...@ke...> - 2008-02-26 07:33:33
|
On Mon, Feb 25, 2008 at 10:42 PM, Alan Sun <new...@gm...> wrote: > My Linux distribution is ST Linux: http://www.stlinux.com/, does anyone > compile and run the latest Valgrind on it? > > Our applications are running on this platform, during the development > process, the memory leak and stack over write is very frequency. So I want > to use Valgrind on this environment, does anyone use this before? It is likely that Valgrind will work on any version of Linux produced since the days of Red Hat 7.3, given that the nightly valgrind builds I see whizzing by on the mailing list mention that operating system. So build it from source and give it a try! But I don't think Valgrind is good at detecting stack overwrites. For that, you need something else. If you have a recent gcc, you might try compiling with -fstack-protector-all, see http://gcc.gnu.org/onlinedocs/gcc-4.2.2//gcc/Optimize-Options.html - Dan |
|
From: Michael A. <Mic...@fs...> - 2008-02-26 07:42:32
|
Dan Kegel wrote: > On Mon, Feb 25, 2008 at 10:42 PM, Alan Sun <new...@gm...> wrote: >> My Linux distribution is ST Linux: http://www.stlinux.com/, does anyone >> compile and run the latest Valgrind on it? >> >> Our applications are running on this platform, during the development >> process, the memory leak and stack over write is very frequency. So I >> want >> to use Valgrind on this environment, does anyone use this before? > > It is likely that Valgrind will work on any version of > Linux produced since the days of Red Hat 7.3, given > that the nightly valgrind builds I see whizzing by on > the mailing list mention that operating system. > So build it from source and give it a try! I guess the issue in this case is not so much the distribution, but the target CPU: This is a Linux distribution targetted at STMicroelectronics Consumer electronics parts which are based around the ST40 or ST200 CPUs. > But I don't think Valgrind is good at detecting stack overwrites. > For that, you need something else. If you have a recent gcc, > you might try compiling with -fstack-protector-all, see > http://gcc.gnu.org/onlinedocs/gcc-4.2.2//gcc/Optimize-Options.html > - Dan Cheers, Michael > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |
|
From: Dan K. <da...@ke...> - 2008-02-26 07:45:03
|
<Mic...@fs...> wrote: > I guess the issue in this case is not so much the distribution, but the > target CPU: > > This is a Linux distribution targetted at STMicroelectronics Consumer > electronics parts which are based around the ST40 or ST200 CPUs. Whoops. Well, the -fstack-protector-all advice might still be useful. Though I suggest the best way to go is get most of the bugs out on x86 before trying to debug on that target system. - Dan |