Summary: | GDB Singe-Step Error: Windows (MinGW) GDB 7.x Under certain conditions, attempts to Single Step result in the error: "Error accessing memory address 0xxxxxxxx: Input/output error" | ||
---|---|---|---|
Product: | gdb | Reporter: | Richard C <fredflintstone> |
Component: | gdb | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | asmwarrior, pedro, tom.boddington |
Priority: | P2 | ||
Version: | unknown | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: | ||
Attachments: | Project files to re-create error and log files |
Description
Richard C
2011-02-16 15:35:14 UTC
Two years on, I am experiencing the very same issues and I see that nobody has been assigned to this bug. Please could somebody give it some attention? A minimal reproducer that just uses gdb (no codeblocks in the picture) would go a long way. Please also try 7.5 and if possible the 7.6 release candidate (bugs in this area have been fixed in 7.6). BTW, that error usually indicates something wrong with gdb's software single-step implementation bit that decides what the PC will be after the instruction being stepped executes (in order to place a breakpoint there). A disassemble of the code that is failed to step would be useful, along with perhaps a "set debug infrun 1" log. Today, I'm testing the project in the attachment under WinXP, PCX's mingw gcc 4.6.3, and GDB CVS build myself, I don't see any issue. I guess such bug is fixed either in GCC or GDB. If you still meet such bug, please post a simple minimal test case. Yuanhui Zhang (Code::Blocks developer) Thanks. Closing as fixed then. Please reopen if more info comes along. |