Message135413
Terry J. Reedy <report@bugs.python.org> wrote:
> "Also, the segfault only occurs when python is
> compiled with optimizations and run under valgrind."
>
> This says to me that the segfault is not a Python issue.
> What change do you expect in the Python source code?
> If none, this issue should be closed.
I think that the passage you quoted is not a strong argument for closing
the issue. I've been using Valgrind for several years, and I've never
encountered a situation where Valgrind was wrong. This includes situations
where a bug only occurs with optimizations turned on.
If anything, the fact that it so far only occurs with gcc-4.3 might
be a reason. Even so, recently an issue was kept open until someone
(I think Victor) proved that it was a compiler bug.
I'm not sure what to make of your question and its conclusion. Debugging
Valgrind issues or compiler bugs takes a lot of time, so the requirement
to pinpoint the exact problem in order to keep an issue open seems too
strict. |
|
Date |
User |
Action |
Args |
2011-05-07 08:03:53 | skrah | set | recipients:
+ skrah, terry.reedy, vstinner, stutzbach |
2011-05-07 08:03:53 | skrah | set | messageid: <1304755433.67.0.680967972906.issue11994@psf.upfronthosting.co.za> |
2011-05-07 08:03:51 | skrah | link | issue11994 messages |
2011-05-07 08:03:51 | skrah | create | |
|