➜
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-04-21 06:19 by loewis, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| test_gdb.txt | loewis, 2010-04-21 06:19 | |||
| Messages (8) | |||
|---|---|---|---|
| msg103803 - (view) | Author: Martin v. Löwis (loewis) *  |
Date: 2010-04-21 06:19 | |
test_gdb fails on 3k; some tests with a message "Error occurred in Python command: No frame is currently selected." A separate problem was reported as #8479; I'm attaching the full test_gdb output. |
|||
| msg103830 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2010-04-21 12:25 | |
I may be related to #8482 (compiler optimization level?). |
|||
| msg103845 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2010-04-21 13:55 | |
libpython.py had a type "PyStringObjectPtr" referencing "PyStringObject" type, whereas Python3 uses "PybytesObject". That's why you got this error. It should be fixed by r80311 (and r80312). |
|||
| msg103853 - (view) | Author: Dave Malcolm (dmalcolm) |
Date: 2010-04-21 15:26 | |
There was a patch for this attached to issue 8380, and you've fixed things in a different way. Should I regenerate a patch against what's now in SVN, or should we use my patch? |
|||
| msg103889 - (view) | Author: Martin v. Löwis (loewis) * |
Date: 2010-04-21 18:53 | |
Victor's patch look fine to me (at least, I can't see a problem with it). If so, we should keep it. In any case, it does fix the problem reported here. |
|||
| msg103903 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2010-04-21 19:59 | |
@Martin: What is your OS? In msg103442 you wrote that you have gdb 7.0.1. Did you try to remove python-gdb.py? (test_gdb should remove and/or update this file!) I tested test_gdb of py3k on Debian Sid (gdb 7.1) and Ubuntu 9.10 (gdb 7.0): I got a lot of errors but I see the gdb backtrace, so the "No frame is currently selected" error is fixed. You should reopen the issue if it's not fixed on your host. |
|||
| msg103904 - (view) | Author: Martin v. Löwis (loewis) * |
Date: 2010-04-21 20:01 | |
See msg103889. I said it's fixed, so I'm not sure what problem you are still trying to solve. |
|||
| msg103906 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2010-04-21 20:23 | |
Oops, I read "it doesn't fix", sorry :-) |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:00 | admin | set | github: 52726 |
| 2010-04-21 20:23:31 | vstinner | set | messages: + msg103906 |
| 2010-04-21 20:01:42 | loewis | set | messages: + msg103904 |
| 2010-04-21 19:59:40 | vstinner | set | messages: + msg103903 |
| 2010-04-21 18:53:40 | loewis | set | messages: + msg103889 |
| 2010-04-21 15:26:07 | dmalcolm | set | assignee: dmalcolm -> loewis messages: + msg103853 |
| 2010-04-21 13:55:39 | vstinner | set | status: open -> closed resolution: fixed messages: + msg103845 |
| 2010-04-21 12:25:30 | vstinner | set | nosy:
+ vstinner messages: + msg103830 |
| 2010-04-21 06:19:12 | loewis | create | |