|
From: Jorge M. <jor...@gm...> - 2010-05-06 20:06:27
|
Dear all, I have a program that makes massif crash reproducibly with a segmentation fault. This occurs in the release version 3.5.0 as well as in one compiled from source today from subversion: valgrind-3.6.0.SVN. The program runs fine in massif 3.3.1 compiled from source. This crash occurs reproducibly in debian sid up to date and OpenSUSE, both amd-64 bit architectures. The program is too large to send away, and I have not been able to make a small test case that reproduces the bug, but I am happy to spend sometime helping to fix this if anyone can tell me what other information I can provide. Thank you, Jorge |
|
From: Bart V. A. <bva...@ac...> - 2010-05-07 10:22:23
|
On Thu, May 6, 2010 at 10:06 PM, Jorge Moraleda <jor...@gm...>wrote: > I have a program that makes massif crash reproducibly with a > segmentation fault. This occurs in the release version 3.5.0 as well > as in one compiled from source today from subversion: > valgrind-3.6.0.SVN. The program runs fine in massif 3.3.1 compiled > from source. This crash occurs reproducibly in debian sid up to date > and OpenSUSE, both amd-64 bit architectures. The program is too large > to send away, and I have not been able to make a small test case that > reproduces the bug, but I am happy to spend sometime helping to fix > this if anyone can tell me what other information I can provide. > Have you already verified whether your program is memcheck-clean ? And if your program is multithreaded, have you already verified whether it is data-race-free ? Bart. |
|
From: Jorge M. <jor...@gm...> - 2010-05-07 22:46:03
|
>> I have a program that makes massif crash reproducibly with a >> segmentation fault. This occurs in the release version 3.5.0 as well >> as in one compiled from source today from subversion: >> valgrind-3.6.0.SVN. The program runs fine in massif 3.3.1 compiled >> from source. This crash occurs reproducibly in debian sid up to date >> and OpenSUSE, both amd-64 bit architectures. The program is too large >> to send away, and I have not been able to make a small test case that >> reproduces the bug, but I am happy to spend sometime helping to fix >> this if anyone can tell me what other information I can provide. > > Have you already verified whether your program is memcheck-clean ? And if > your program is multithreaded, have you already verified whether it is > data-race-free ? Thank you. memcheck runs fine through program completion and reports no leaks. drd runs fine through program completion, and it reports a small number of race conditions that seem related to std::locale::locale(). I am working on that and have already asked for help in this group. I am working on creating a small example that reproduces the errors so I can ask a more detailed question, but I have not yet succeeded. cachegrind crashes, at what seems the same point than massif crashes based on program output. I have not used cachegrind before, so I don't know much about it. Jorge > > Bart. > |