| Summary: | When debugging through KDevelop, I get a M1 Type Error | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Steven Sroka <Sroka.Steven> |
| Component: | CPP Debugger | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | batyiev, Sroka.Steven |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | 4.2.0 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot of error message | ||
What gdb version do you use? Do you use .gdbinit file or any other gdb startup tuning? waiting for user info I use version 7.2-1ubuntu11. I haven't personally added/edited any gdb files. I also just did a search of my linux partition and I could not find tht file. Git commit 6a681b77de3f5552d61eff6b5b79ad7c8e3f3535 by Niko Sams. Committed on 07/06/2011 at 19:48. Pushed by nsams into branch 'master'. Fix Internal Debugger Error when clicking step into too fast Always wait for a gdb reply (^done or ^running) before sending the next command. *stopped is not a reply, as ^done will follow and everything will get out of sync. Also remove a workaround for handling attach response, as this had apperently the same problem. BUG: 274390 M +16 -23 debuggers/gdb/gdb.cpp M +3 -0 debuggers/gdb/gdb.h A +29 -0 debuggers/gdb/unittests/debugeeqt.cpp [License: LGPL (v2)] M +17 -0 debuggers/gdb/unittests/gdbtest.cpp M +1 -0 debuggers/gdb/unittests/gdbtest.h http://commits.kde.org/kdevelop/6a681b77de3f5552d61eff6b5b79ad7c8e3f3535 |
Created attachment 60420 [details] Screenshot of error message Version: unspecified (using KDE 4.6.3) OS: Linux I can't debug my programming without getting a M1 Type Error in the middle of sepping through the code. I can continue after I get the error message though. Reproducible: Always Steps to Reproduce: Build a project. Click "Debug". Press "Step Into" a few times (x5 times or so). Actual Results: A dialog box appears with an error message. See attachment. Expected Results: Debugger to complete successfully. I'm using version 4.2.2 (this version option is not listed in the dropdown menu on the bug form)