1In no particular order: 2 3Fix "utils.c:98:30: warning: logical not is only applied to the left hand 4side of comparison" - insifnificant, swapping should be enough. 5 6Request a (min?) height of 80 for the GtkTextView-s, for gtk+3 only. 7gtk+2 works fine. 8 9Don't allow Run/Continue without a program or script specified, it's almost 10always a mistake, but allow an empty script, even the system null file. 11Simplify the startup sequence. Simplify the Program Setup dialog, block OK 12if neither program nor script is specified. Update the documentation. 13 14Replace the "Temporary breakpoint on load" with "Break on startup", using 15gdb 7.7+ -exec-run --start. Simplify the startup sequence. Place a label 16near the checkbox that gdb 7.7 is required. Update the documentation. 17Convert the temporary location if any to a regular breakpoint?.. 18 19Windows: add "Break on ExitProcess" and "Break on TerminateProcess" to 20Debug -> More?.. Useful for stopping at console program exit, since the 21console now closes automatically. 22 23Write more friendly documentation. The current one now seems a bit haughty. 24 25Add a setting for the gdb version, along with a "Detect" button? We only 26need it for -exec-run --start, the double-escape bug under in the Windows 27breakpoint list (fixed between 7.6.1 and 7.9.1) and the var-update bug, 28which was fixed at some point. Doesn't seem worth. 29 30Add a (renew the?) PR for the project-before-save signal. 31 32Correct locale from/to utf8 for variables under Windows: utils_get_...() 33from Geany should be g_locale_from/to_utf8(). Maybe provide a default Auto 34setting which detects utf8-or-locale? 35 36Add a [ ] Pending checkbox in the breakpoints menu? Currently a breakpoint 37that succeeds can't be marked as pending for the next child runs. 38 39Create a PR for ui_setup_open_button_callback. It was discussed long time 40ago, but ended without a resolution. 41 42"No breakpoints. Hanging." - with a program or script always present, this 43should be a per-program option. Also improve the text. 44 45Per-program gdb executable. 3-rd tab "GDB" in the Program Setup dialog. Move 46the gdb prefs there, including the bugs. Verify that the registers are 47re-queried on gdb change. A few more gdb options, maybe CL options too, for 48example --quiet, but only ones that can't be set via script. 49 50set_error -> set_error_literal where the text is static. 51 52Setup Program _Import -> I_mport, the underline is too short now. Add _Help, 53call the browser at #set_program. 54 55Add a note in the documentation that the memory offset, count can't be saved 56because of variable address/size changes on recompilation. Add a ^(Scope) 57command for inspecting memory. 58 59Change the "=li_brary" in the che label to "=li_brary-...", add a TL note 60that the "=library-..." text must not be translated, but the underline may 61be moved anywhere. 62 63Add a note that "[ ] Show Tooltips" requires restart (does it?..) 64 65GDB has an option to add the command execution times to MI, alter the parser 66to ignore them. 67 68Convert the thread exit codes to decimal. Options for decimal/hex/as-is? 69 70Write a Preferences dialog for the global preferences? 71 72wchar_t / L"text" support? 73 74Save sort column #-s? 75 76Check what's new in 7.7 and later. Add --language=C to all commands that 77produce variable texts? "--skip-unavailable"? Better support for 78catchpoints? 79 80Use the new plugin startup that allows failure, and check for the glade 81file? 82 83Per-program options to hide views: Program Terminal, Threads, Memory, 84Debug Console, Registers. 85 86Add a ^(Scope) command for (de)activating breakpoint groups and a 87on_break_signal() handler: a-h activate, A-H deactivate. Add a single letter 88(none, a-h) Group submenu to the breakpoints menu. 89 90Set breakpoint by clicking on the empty space before of a line, where the 91markers are shown. 92 93Message "<thread X | Program> received signal Y"? 94 95Try DND-selected-text support for Watches, Inspect? 96 97Try Watch formats or radix. 98 99Mark "Delete all breakpoints, watches ..." with bold if the program or 100script name was changed. 101 102Add a second Memory page? (Supporting 2+ regions in a single page seems 103confusing and uncomfortable UI.) 104 105Max display length for MI? Should try some very long lines, to see whether 106that makes sense. Failed MI must be fully displayed in all cases. 107 108Disassembler read-only editor window using the gdb commands only. Auto open 109on assembler location hit. That'll take some work. 110 111Remember 3 lines around the breakpoints and try to apply them as in patch, 112in the case that source was modified without the breakpoints loaded. That'll 113take work, too. 114