https://bugs.kde.org/show_bug.cgi?id=446786

            Bug ID: 446786
           Summary: gdb front end fails for certain .gdbinit files
                    (noticed with https://github.com/hugsy/gef)
           Product: kdevelop
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: CPP Debugger
          Assignee: kdevelop-bugs-n...@kde.org
          Reporter: david_oldf...@hotmail.com
                CC: niko.s...@gmail.com
  Target Milestone: ---

Created attachment 144432
  --> https://bugs.kde.org/attachment.cgi?id=144432&action=edit
the error message I get

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. install GEF 
2. Attempt to debug a C/C++ project with gdb


OBSERVED RESULT
debugging will fail to start and you'll get a drop down message that your
version of gdb is too old with escaped binary in place of info about gdb that
should have been detected


EXPECTED RESULT
I'm not really sure the best way to handle it and the expected result would
depend on that. Either the debugger would work as expected or the error message
would be fixed with a hint about the .gdbinit file.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: This should apply to all versions and any oses that support
gdb I tested with Kubuntu 21.10 plasma 5.22.5
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
if gdb were run with -nx it would not load a .gdbinit file. I've used gdb for
reverse engineering on occasion, but rarely for CTFs so I'm not really familiar
with the power of .gdbinit files and I'm not sure if kdevelop can cope with
.gdbinit files other than gef or if there could be value in loading them?. I
have a feeling this solution makes the most sense. The alternative would
require altering the regex used to look for gdb version information and
altering the error message given when kdevelop thinks debugging can't work.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to