Summary: | Callgrind segfaults upon call of some boost::spirit routines | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Sebastian Steiger <steiger> |
Component: | callgrind | Assignee: | Josef Weidendorfer <josef.weidendorfer> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | jseward, nate |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Sebastian Steiger
2010-06-02 18:44:54 UTC
I forgot to mention that an empty file "boost_test.in" must be present in order for the test case to run. Possibly the same bug as 197988. Sebastian, try out the fix at https://bugs.kde.org/show_bug.cgi?id=197988#c44 Thanks for the quick reply. Indeed this bug is a duplicate of 197988. I was using the Kubuntu repository package for valgrind before, so I now downloaded and installed valgrind-3.5.0 to be able and modify the source code. I checked that without modifications the segfault is still there. Then I changed coregrind/pub_core_aspacemgr.h: # define VG_STACK_ACTIVE_SZB (4096 * 512) // 2Mb I recompiled and ran the test again, and now it works! Am I going to see this fix in one of the later Kubuntu repository packages? Two side notes: - I needed to modify the 3.5.0 configure script because Kubuntu 10.04 has glibc 2.11 which is not yet handled in it. - When I try to use the current SVN version of valgrind, it immediately aborts with the following message: valgrind: mmap(0x400000, 114688) failed in UME with error 22 (Invalid argument). This happens even when valgrinding the simplest "Hello World" program. Sebastian (In reply to comment #3) > I recompiled and ran the test again, and now it works! Am I going to see this > fix in one of the later Kubuntu repository packages? This fix will be in the next release (3.6.0). > - When I try to use the current SVN version of valgrind, it immediately aborts > with the following message: > > valgrind: mmap(0x400000, 114688) failed in UME with error 22 (Invalid > argument). Yes. This is due to a very recent change (r11141). Am still trying to figure out how to fix it. See https://bugs.kde.org/show_bug.cgi?id=193413#c18 for the gory details. (In reply to comment #4) > > - When I try to use the current SVN version of valgrind, it immediately aborts > > with the following message: > > > > valgrind: mmap(0x400000, 114688) failed in UME with error 22 (Invalid > > argument). > > Yes. This is due to a very recent change (r11141). Am still trying > to figure out how to fix it. See > https://bugs.kde.org/show_bug.cgi?id=193413#c18 > for the gory details. Possibly fixed now by r11146. Give it a try. (In reply to comment #5) > (In reply to comment #4) > > > - When I try to use the current SVN version of valgrind, it immediately aborts > > > with the following message: > > > > > > valgrind: mmap(0x400000, 114688) failed in UME with error 22 (Invalid > > > argument). > > > > Yes. This is due to a very recent change (r11141). Am still trying > > to figure out how to fix it. See > > https://bugs.kde.org/show_bug.cgi?id=193413#c18 > > for the gory details. > > Possibly fixed now by r11146. Give it a try. Yes, it seems to be fixed. Also the glibc-2.11 issue is fixed I believe. Thanks! I performed the following: svn update ./autogen.sh ./configure make clean make --prefix=$PWD make install *** This bug has been marked as a duplicate of bug 197988 *** | CLOSES CLOSES |