Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#25818 - [gdb]
Attached to Project:
Arch Linux
Opened by Nathan (DigitalPioneer) - Monday, 29 August 2011, 21:05 GMT
Last edited by Allan McRae (Allan) - Thursday, 01 September 2011, 06:53 GMT
Opened by Nathan (DigitalPioneer) - Monday, 29 August 2011, 21:05 GMT
Last edited by Allan McRae (Allan) - Thursday, 01 September 2011, 06:53 GMT
|
DetailsDescription:
This latest package of gdb breaks debugging in KDevelop. Sometimes KDevelop's internal commands to gdb give errors and unfortunate behavior results, such as the debugged program being set free to run to completion without breaking at my breakpoints. GDB package 7.3-1 works correctly, this issue was introduced in package 7.3-2. Apparently, some change between pkgver 1 and 2 changed the way GDB interprets commands, causing it to mishandle input from KDevelop. Additional info: * package version(s) 7.3-2 * config and/or log files etc. In this log of commands to GDB, the issue is repeated several times: http://pastebin.com/k8GLpmWt Steps to reproduce: I was unable to reproduce this issue in a project other than the one I first noticed it in. Sorry. :( |
This task depends upon
Closed by Allan McRae (Allan)
Thursday, 01 September 2011, 06:53 GMT
Reason for closing: None
Additional comments about closing: See comments
Thursday, 01 September 2011, 06:53 GMT
Reason for closing: None
Additional comments about closing: See comments
Comment by Nathan (DigitalPioneer) -
Monday, 29 August 2011, 21:13 GMT
I just remembered that 7.3-2 was made because 7.3-1 didn't have python support enabled... So, everything used to work right in 7.3-2 also, but it doesn't now. In 7.3-1 I can debug my program, but the python support is gone.
Comment by Allan McRae (Allan) -
Thursday, 01 September 2011, 04:04 GMT
This sounds more like an issue with your KDevelop project file than a gdb issue. Especially if everything used to work right with gdb-7.3-2. Given everything still works with gdb-7.3-1, perhaps it is a python script you are using with gdb?
Comment by Nathan (DigitalPioneer) -
Thursday, 01 September 2011, 04:11 GMT
Yes, you may well be right. When I reported this, I had forgotten that 7.3-1 had no python support, so that might have been the source of my problems. I thought perhaps the update had broken something. Plus, the kdevelop folks are fairly confident that it's not their bug. But I'm beginning to think it's not a gdb issue after all. In any event, I don't think we have enough to say for sure. Since I can't reproduce the issue in another project, I think we can close this issue.
Comment by Allan McRae (Allan) -
Thursday, 01 September 2011, 06:52 GMT
OK - I will close this given this can not be reproduced elsewhere. Feel free to request a reopen if needed.