aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2018-11-26Automatic date update in version.inGDB Administrator1-1/+1
2018-11-25Automatic date update in version.inGDB Administrator1-1/+1
2018-11-24Automatic date update in version.inGDB Administrator1-1/+1
2018-11-23Automatic date update in version.inGDB Administrator1-1/+1
2018-11-22Automatic date update in version.inGDB Administrator1-1/+1
2018-11-21Make command-repeat work after gdb.executeBenno Fünfstück4-1/+15
Since commit 56bcdbea2bed ("Let gdb.execute handle multi-line commands") command repetition after using the `gdb.execute` Python function fails (the previous command is not repeated anymore). This happens because read_command_lines_1 sets dont_repeat, but the call to prevent_dont_repeat in execute_gdb_command is later. The fix is to move the call to prevent_dont_repeat to the beginning of the function. Tested on my laptop (ArchLinux-x86_64). gdb/ChangeLog: PR python/23714 * gdb/python/python.c (execute_gdb_command): Call prevent_dont_repeat earlier to avoid affecting dont_repeat. gdb/testuite/ChangeLog: PR python/23714 * gdb.python/python.exp: Test command repetition after gdb.execute.
2018-11-21Automatic date update in version.inGDB Administrator1-1/+1
2018-11-20Automatic date update in version.inGDB Administrator1-1/+1
2018-11-19gdb.base/warning.exp tweaksPedro Alves2-5/+11
#1- Check that the warning is emitted. #2- Avoid overriding INTERNAL_GDBFLAGS, as per documentated in gdb/testsuite/README: ~~~ The testsuite does not override a value provided by the user. ~~~ We don't actually need to tweak INTERNAL_GDBFLAGS, we just need to append out -data-directory to GDBFLAGS, because each passed -data-directory option leads to a call to the warning: $ ./gdb -data-directory=foo -data-directory=bar Warning: foo: No such file or directory. Warning: bar: No such file or directory. [...] 2018-11-19 Pedro Alves <palves@redhat.com> * gdb.base/warning.exp: Don't override INTERNAL_FLAGS. Use gdb_spawn_with_cmdline_opts instead of gdb_start. Check that we see the expected warning.
2018-11-19Avoid crash when calling warning too earlyTom Tromey5-3/+59
I noticed that if you pass the name of an existing file (not a directory) as the argument to --data-directory, gdb will crash: $ ./gdb -nx --data-directory ./gdb ../../binutils-gdb/gdb/target.c:590:56: runtime error: member call on null pointer of type 'struct target_ops' This was later reported as PR gdb/23838. This happens because warning ends up calling target_supports_terminal_ours, which calls current_top_target, which returns nullptr this early. This fixes the problem by handling this case specially in target_supports_terminal_ours. I also changed target_supports_terminal_ours to return bool. 2018-11-08 Tom Tromey <tom@tromey.com> PR gdb/23555: PR gdb/23838: * target.h (target_supports_terminal_ours): Return bool. * target.c (target_supports_terminal_ours): Handle case where current_top_target returns nullptr. Return bool. gdb/testsuite/ChangeLog 2018-11-08 Tom Tromey <tom@tromey.com> PR gdb/23555: PR gdb/23838: * gdb.base/warning.exp: New file.
2018-11-19Automatic date update in version.inGDB Administrator1-1/+1
2018-11-18Automatic date update in version.inGDB Administrator1-1/+1
2018-11-17Automatic date update in version.inGDB Administrator1-1/+1
2018-11-16Automatic date update in version.inGDB Administrator1-1/+1
2018-11-15Automatic date update in version.inGDB Administrator1-1/+1
2018-11-14Automatic date update in version.inGDB Administrator1-1/+1
2018-11-13Automatic date update in version.inGDB Administrator1-1/+1
2018-11-12Automatic date update in version.inGDB Administrator1-1/+1
2018-11-11Automatic date update in version.inGDB Administrator1-1/+1
2018-11-10Automatic date update in version.inGDB Administrator1-1/+1
2018-11-09Automatic date update in version.inGDB Administrator1-1/+1
2018-11-08Automatic date update in version.inGDB Administrator1-1/+1
2018-11-07Automatic date update in version.inGDB Administrator1-1/+1
2018-11-06Automatic date update in version.inGDB Administrator1-1/+1
2018-11-05Automatic date update in version.inGDB Administrator1-1/+1
2018-11-04Automatic date update in version.inGDB Administrator1-1/+1
2018-11-03Automatic date update in version.inGDB Administrator1-1/+1
2018-11-02Automatic date update in version.inGDB Administrator1-1/+1
2018-11-01Automatic date update in version.inGDB Administrator1-1/+1
2018-10-31Automatic date update in version.inGDB Administrator1-1/+1
2018-10-30Automatic date update in version.inGDB Administrator1-1/+1
2018-10-29Automatic date update in version.inGDB Administrator1-1/+1
2018-10-28Automatic date update in version.inGDB Administrator1-1/+1
2018-10-27Automatic date update in version.inGDB Administrator1-1/+1
2018-10-26Automatic date update in version.inGDB Administrator1-1/+1
2018-10-25Automatic date update in version.inGDB Administrator1-1/+1
2018-10-24Automatic date update in version.inGDB Administrator1-1/+1
2018-10-23Automatic date update in version.inGDB Administrator1-1/+1
2018-10-22Automatic date update in version.inGDB Administrator1-1/+1
2018-10-21Automatic date update in version.inGDB Administrator1-1/+1
2018-10-20Automatic date update in version.inGDB Administrator1-1/+1
2018-10-19Automatic date update in version.inGDB Administrator1-1/+1
2018-10-18Automatic date update in version.inGDB Administrator1-1/+1
2018-10-17Automatic date update in version.inGDB Administrator1-1/+1
2018-10-16Automatic date update in version.inGDB Administrator1-1/+1
2018-10-15Automatic date update in version.inGDB Administrator1-1/+1
2018-10-14Automatic date update in version.inGDB Administrator1-1/+1
2018-10-13Automatic date update in version.inGDB Administrator1-1/+1
2018-10-12Automatic date update in version.inGDB Administrator1-1/+1
2018-10-11Automatic date update in version.inGDB Administrator1-1/+1