This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2010年11月05日 21:30 by pitrou, last changed 2022年04月11日 14:57 by admin. This issue is now closed.
| Messages (5) | |||
|---|---|---|---|
| msg120537 - (view) | Author: Antoine Pitrou (pitrou) * (Python committer) | Date: 2010年11月05日 21:30 | |
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) Ensure that a PyObject* with NULL ob_type is handled gracefully ---------------------------------------------------------------------- Traceback (most recent call last): File "/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-ppc/build/Lib/test/test_gdb.py", line 390, in test_NULL_ob_type 'set v->ob_type=0') File "/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-ppc/build/Lib/test/test_gdb.py", line 361, in assertSane cmds_after_breakpoint=cmds_after_breakpoint) File "/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-ppc/build/Lib/test/test_gdb.py", line 150, in get_gdb_repr import_site=import_site) File "/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-ppc/build/Lib/test/test_gdb.py", line 132, in get_stack_trace self.assertEquals(err, '') AssertionError: '\nwarning: not using untrusted file "/home/barry/.gdbinit"\n' != '' - - warning: not using untrusted file "/home/barry/.gdbinit" See http://www.python.org/dev/buildbot/builders/PPC%20Ubuntu%203.x/builds/0/steps/test/logs/stdio |
|||
| msg120538 - (view) | Author: Dave Malcolm (dmalcolm) (Python committer) | Date: 2010年11月05日 21:40 | |
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 |
|||
| msg120540 - (view) | Author: Dave Malcolm (dmalcolm) (Python committer) | Date: 2010年11月05日 21:53 | |
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 fixed on the buildbot? |
|||
| msg120542 - (view) | Author: Barry A. Warsaw (barry) * (Python committer) | Date: 2010年11月05日 21:56 | |
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) |
|||
| msg120807 - (view) | Author: Dave Malcolm (dmalcolm) (Python committer) | Date: 2010年11月08日 21:52 | |
Closing "won't fix", since this was misconfiguration; filtering out such warnings might mask a security issue. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:57:08 | admin | set | github: 54540 |
| 2010年11月08日 21:52:45 | dmalcolm | set | status: open -> closed resolution: wont fix messages: + msg120807 |
| 2010年11月05日 21:56:22 | barry | set | messages: + msg120542 |
| 2010年11月05日 21:53:41 | dmalcolm | set | messages: + msg120540 |
| 2010年11月05日 21:40:54 | dmalcolm | set | messages: + msg120538 |
| 2010年11月05日 21:30:25 | pitrou | create | |