Summary: | global variables in debugger | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Jon Smirl <jonsmirl> |
Component: | CPP Debugger | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | git master | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jon Smirl
2004-01-08 20:32:08 UTC
Wish. I think this can be problematic. "info variables" in gdb will print all global variables, including those from libstd++, such as: const _Ios_Fmtflags std::ios_base::boolalpha; const _Ios_Fmtflags std::ios_base::dec; const _Ios_Iostate std::ios_base::eofbit; const _Ios_Iostate std::ios_base::failbit; and all static constants for all classes. For a simple app, I get several pages, and all symbols are reported to be defined in my .cpp file. Unless there's some sensible way to filter irrelevant variables, adding them all to variables view would not help. as far as I can see this is a wontfix, especially as you can just add a watch for your global variables. |