- 08 Feb, 2020 2 commits
-
-
Joel Brobecker authored
gdb/ChangeLog: * version.in: Set GDB version number to 9.1.
-
GDB Administrator authored
-
- 07 Feb, 2020 4 commits
-
-
Iain Buclaw authored
This patch redefines fputs_unfiltered in utils.c, with new behavior to forward parameters to fputs_maybe_filtered. This makes fputs_unfiltered identical to fputs_filtered, except filtering is disabled. Some callers of fputs_unfiltered have been updated to use ui_file_puts where they were using other ui_file_* functions anyway for IO. This fixes the problem I saw with \032\032post-prompt annotation being flushed to stdout in the wrong order. gdb/ChangeLog 2020-02-05 Iain Buclaw <ibuclaw@gdcproject.org> PR gdb/25190: * gdb/remote-sim.c (gdb_os_write_stderr): Update. * gdb/remote.c (remote_console_output): Update. * gdb/ui-file.c (fputs_unfiltered): Rename to... (ui_file_puts): ...this. * gdb/ui-file.h (ui_file_puts): Add declaration. * gdb/utils.c (emit_style_escape): Update. (flush_wrap_buffer): Update. (fputs_maybe_filtered): Update. (fputs_unfiltered): Add function. Change-Id: I17ed5078f71208344f2f8ab634a6518b1af6e213 -
Iain Buclaw authored
This changes gdb_flush to also flush the internal wrap buffer. A few places needed to continue using the previous approach, so this also introduces ui_file_flush for those. gdb/ChangeLog 2020-02-05 Iain Buclaw <ibuclaw@gdcproject.org> * gdb/event-loop.c (gdb_wait_for_event): Update. * gdb/printcmd.c (printf_command): Update. * gdb/remote-fileio.c (remote_fileio_func_write): Update. * gdb/remote-sim.c (gdb_os_flush_stdout): Update. (gdb_os_flush_stderr): Update. * gdb/remote.c (remote_console_output): Update. * gdb/ui-file.c (gdb_flush): Rename to... (ui_file_flush): ...this. (stderr_file::write): Update. (stderr_file::puts): Update. * gdb/ui-file.h (gdb_flush): Rename to... (ui_file_flush): ...this. * gdb/utils.c (gdb_flush): Add function. * gdb/utils.h (gdb_flush): Add declaration. Change-Id: I7ca143d30f03dc39f218f6e880eb9bca9e15af39 -
Tom Tromey authored
Commit a0c1ffed regressed certain cases coming from Eclipse. See PR breakpoints/24915. This patch reverts the commit for the gdb 9 release. gdb/ChangeLog 2020-02-07 Tom Tromey <tromey@adacore.com> PR breakpoints/24915: * source.c (find_and_open_source): Do not check basenames_may_differ. gdb/testsuite/ChangeLog 2020-02-07 Tom Tromey <tromey@adacore.com> PR breakpoints/24915: * gdb.base/annotate-symlink.exp: Use setup_xfail. Change-Id: Iadbf42f35eb40c95ad32b2108ae25d8f199998bd
-
GDB Administrator authored
-
- 06 Feb, 2020 1 commit
-
-
GDB Administrator authored
-
- 05 Feb, 2020 1 commit
-
-
GDB Administrator authored
-
- 04 Feb, 2020 1 commit
-
-
GDB Administrator authored
-
- 03 Feb, 2020 1 commit
-
-
GDB Administrator authored
-
- 02 Feb, 2020 1 commit
-
-
GDB Administrator authored
-
- 01 Feb, 2020 3 commits
-
-
Sergio Durigan Junior authored
The generation of snapshots has been broken since we've disable in-tree builds for GDB. Given that src-release.sh performs a build before creating the release tarball, and that this build is performed in-tree, the solution we found is to implement a new top-level configure flag called '--enable-src-release-build' which disables the in-tree build restriction, and then make src-release.sh use it. ChangeLog: 2020-02-01 Sergio Durigan Junior <sergiodj@redhat.com> Eli Zaretskii <eliz@gnu.org> * configure.ac: Don't abort the build if trying to build GDB in tree _and_ invoking with '--enable-src-release-build'. * configure: Regenerate. * src-release.sh (do_proto_toplev): Invoke 'configure' using Change-Id: Ic6dd55accd9a03e62fe498f7fd704fb67f44bfa9
-
Eli Zaretskii authored
This commit fixes a compilation failure in a couple of libctf files due to the use of EOVERFLOW and ENOTSUP, which are not defined when compiling on MinGW. libctf/ChangeLog: PR binutils/25155: * ctf-create.c (EOVERFLOW): If not defined by system header, redirect to ERANGE as a poor man's substitute. * ctf-subr.c (ENOTSUP): If not defined, use ENOSYS instead. This one is how Eli implemented it. I think this implementation has a weakness in the following sense: If other units in libctf start using those constants, we'll get the same error again. Also, I'm wondering whether their use is documented as part of the official libtcf API or not -- users might be writing code that tests for these, and if the system doesn't support them, how would they know what errno code to use in its place. This argues for a having that information in one of libctf's header files. I think it would be nice to have those in ctf-decls.h, but I think we'll need to include <errno.h> in ctf-decls.h if we decide to define those macros there. Rather than second-guess what the CTF developers would prefer, I'm starting by sending Eli's patch, to see what you guys think. Thanks, -- Joel
-
GDB Administrator authored
-
- 31 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 30 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 29 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 28 Jan, 2020 2 commits
-
-
Hannes Domani authored
The address was written as a long value, but long is always a 32bit value on Windows, which lead to truncated addresses. The solution was to use paddress instead. gdb/gdbserver/ChangeLog: 2020-01-28 Hannes Domani <ssbssa@yahoo.de> * server.c (handle_qxfer_libraries): Write segment-address with paddress.
-
GDB Administrator authored
-
- 27 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 26 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 25 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 24 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 23 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 22 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 21 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 20 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 19 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 18 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 17 Jan, 2020 2 commits
-
-
Joel Brobecker authored
The move of gnulib to the top src directory is causing the GDB build to break if configured in tree. We hope to lift that limitation at some point but, in the meantime, this commit allows us to abort the initial configure right away with a clear error message should the user attempt to build in tree. ChangeLog: * configure.ac: Abort the build with an error if trying to build GDB in tree. * configure: Regenerate. -
GDB Administrator authored
-
- 16 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 15 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 14 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 13 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 12 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 11 Jan, 2020 1 commit
-
-
GDB Administrator authored
-
- 10 Jan, 2020 2 commits
-
-
Christian Biesinger authored
Recent MinGW versions require -lssp when using _FORTIFY_SOURCE, which gdb does (in common-defs.h) https://github.com/msys2/MINGW-packages/issues/5868#issuecomment-544107564 To avoid all the complications with checking for -lssp and making sure it's linked statically, just don't define it. gdb/ChangeLog: 2020-01-10 Christian Biesinger <cbiesinger@google.com> * gdbsupport/common-defs.h: Don't define _FORTIFY_SOURCE on MinGW. Change-Id: Ide6870ab57198219a2ef78bc675768a789ca2b1d
-
GDB Administrator authored
-
- 09 Jan, 2020 1 commit
-
-
GDB Administrator authored
-