[issue10331] test_gdb failure when warnings printed out

Dave Malcolm added the comment: Closing "won't fix", since this was misconfiguration; filtering out such warnings might mask a security issue. -- resolution: -> wont fix status: open -> closed ___ Python tracker

[issue10331] test_gdb failure when warnings printed out

Barry A. Warsaw added the comment: It is a misconfiguration. I started my new buildbot with my environment active. I've since killed that and restarted it with a clean ~buildbot environment. So we shouldn't see this in my buildbots any more. (FWIW, ~/.gdbinit is 644) -- _

[issue10331] test_gdb failure when warnings printed out

Dave Malcolm added the comment: Alternatively, it looks like having it owned by another user would do this. For curiosity's sake, what's the output of: ls -al /home/barry/.gdbinit on that buildbot? Given that it's a security warning, should this simply be treated as misconfiguration, and be

[issue10331] test_gdb failure when warnings printed out

Dave Malcolm added the comment: Seems to relate to this gdb feature: http://sourceware.org/ml/gdb-patches/2005-05/msg00637.html Barry: is your ~/.gdbinit world writable? I can cook up a patch to ignore such warnings -- ___ Python tracker

[issue10331] test_gdb failure when warnings printed out

New submission from Antoine Pitrou : There is this kind of failures on Barry's new buildbot. It looks like warning messages should be ignored when checking gdb output: == FAIL: test_NULL_ob_type (test.test_gdb.PrettyPrintTests