Laurent Morichetti [Thu, 23 Apr 2020 23:36:39 +0000 (16:36 -0700)]
Set the vector registers type's name
The "maintenance print register-groups" command reported the vector
registers type did not have a name, so set the name when we create it.
Before:
(gdb) maintenance print register-groups
Name Nr Rel Offset Size Type Groups
v0 0 0 0 256 *1 all,general,vector
...
*1: Register type's name NULL.
After:
(gdb) maintenance print register-groups
Name Nr Rel Offset Size Type Groups
v0 0 0 0 256 int32_t[64] all,general,vector
...
Change-Id: I17fc4ddad488186f44f166dfd3577b33d80e98ad
Laurent Morichetti [Thu, 23 Apr 2020 17:48:20 +0000 (10:48 -0700)]
Use the process's comm value for GPU threads name
Instead of using the dispatched kernel's name as the thread name,
use the process's comm value. This will match the CPU threads, and
still allow to differentiate threads from different inferiors.
Change-Id: I0746f1d4cdbdd44e9f0ea65997ca9be80ef95bb6
Qingchuan Shi [Thu, 13 Feb 2020 16:19:17 +0000 (11:19 -0500)]
Add new multi-GPU multi-func test in gdb.rocm.
Change-Id: I682b5502f9bc4fad963b1d650b4128c3da1e0bb5
Laurent Morichetti [Sat, 18 Apr 2020 00:37:26 +0000 (17:37 -0700)]
Check the amd-dbgapi library version
Make sure the loaded debugger library version is greater than or
equal to the one used to build ROCgdb.
Change-Id: I6a651a721c1e3066a6f95a15caebbe1d207eda87
Simon Marchi [Wed, 8 Jan 2020 16:39:29 +0000 (11:39 -0500)]
Change regcache list to be an hash map
The regcache objects created for threads are stored in a linked list,
regcache::current_regcache.
This may result in bad performance when debugging a lot of threads, as GDB
needs to walk the linked list to fetch a regcache given a ptid.
This patch replaces the linked list with an std::unordered_map, indexed by
(ptid, arch). The lookups, in get_thread_arch_aspace_regcache, should become
faster when the number of threads grow. With a small number of threads, it
will probably be a bit slower to do an hash map lookup than to walk a few
linked list nodes, but it should not be perceptible.
The function registers_changed_ptid deletes all regcaches related to a given
ptid (there could be multiple, with different arches). Since the hash map is
indexed by (ptid, arch), we can't do a simple lookup, so we fall back on
iterating on all the hash map values. It should be the same complexity as what
we have today. This function is called when resuming execution, so it would be
nice to find a more efficient way to do this.
Similarly, the function regcache_thread_ptid_changed is called when a thread
changes ptid, so it needs to look up all regcaches for a given ptid. This one
also iterates on all the hash map values. However, it is not called often
(mostly when creating an inferior, on some specific platforms), so it shouldn't
be a problem.
Change-Id: I01c9af327b472422b432b71b6c4737424839d254
Simon Marchi [Tue, 3 Dec 2019 20:19:35 +0000 (15:19 -0500)]
Make find_thread_ptid lookup thread map instead of iterate
Now that inferior threads are stored in a map, change the
find_thread_ptid function to look up a thread using std::map::find,
instead of iterating on all of the inferior's threads.
Change-Id: I0041380775fa2bfffdb6e78847d980015b670708
Simon Marchi [Thu, 19 Dec 2019 19:19:41 +0000 (14:19 -0500)]
Change inferior thread list to be a thread map
Remove the inferior::thread_list linked list, replace with
inferior::thread_map, an std::map indexed by ptid. This should make it
faster to look up a thread from its ptid.
Change-Id: I0ac4832542d8427625e330ff9dc3e7f989b164e8
Simon Marchi [Thu, 19 Dec 2019 19:19:15 +0000 (14:19 -0500)]
Fix indentation in print_thread_info_1
Change-Id: Ic18155aea3fb2df4e3428f5f5d5ad4e727160b85
Laurent Morichetti [Wed, 1 Apr 2020 01:09:44 +0000 (18:09 -0700)]
Handle code object URIs
The URI is decoded and the file is opened on the target. Only
file:// is currently supported.
Change-Id: Ifc7869cab60b98f6d4f1645fc2f4ab7c1c767b6d
Laurent Morichetti [Tue, 10 Mar 2020 21:24:29 +0000 (14:24 -0700)]
Update get_os_pid
Return AMD_DBGAPI_STATUS_ERROR_PROCESS_EXITED if the process has
exited.
Change-Id: Ibb9137552e74628ec46633d18f88473fd8b97195
Laurent Morichetti [Tue, 10 Mar 2020 21:23:19 +0000 (14:23 -0700)]
Error message cleanup
Don't print an error message when reading/writing memory fails,
only return TARGET_XFER_EOF.
Change-Id: Iba9c8279e6f5db37344c5eeb8d45cc56902c90ab
Qingchuan Shi [Wed, 4 Mar 2020 15:49:45 +0000 (10:49 -0500)]
re-organize rocm gdb test to follow gdb test naming convention.
Change-Id: Ib2c4f9894dbd9de91e23a041c61c83c20c9cbaad
rohit pathania [Mon, 27 Jan 2020 13:55:55 +0000 (08:55 -0500)]
modified ROCm Thread to AMDGPU Thread in test
Change-Id: I459797d5b8138228d99d34d41e24ce96517f4368
Laurent Morichetti [Sat, 15 Feb 2020 21:35:09 +0000 (13:35 -0800)]
amdgcn: Add Navi1x support
bfd ChangeLog:
* archures.c: Add gfx10 definitions.
* cpu-amdgcn.c: Likewise.
* elf64-amdgcn.c: Likewise.
Change-Id: Ieb4dd551836a990d2cdc883f6d7e52984f6dd9e3
Laurent Morichetti [Thu, 13 Feb 2020 01:46:38 +0000 (17:46 -0800)]
Update the documentation
Add additional packages needed to generate the documentation on CentOS.
Change-Id: I355f3a95d4f484ab746e3d3985a031df5c0b24e5
Tony [Mon, 10 Feb 2020 11:21:50 +0000 (06:21 -0500)]
Correct README-ROCM.md spelling
Change-Id: I0940dad0e54161bb4d0f869944722eb6eb8ec443
Laurent Morichetti [Mon, 10 Feb 2020 22:56:03 +0000 (14:56 -0800)]
Merge branch 'gdb-9-branch' into amd-staging-rocgdb-9
Change-Id: I87c1d275efe8128a2615286a6192e3e7163545a4
Joel Brobecker [Sat, 8 Feb 2020 12:50:15 +0000 (16:50 +0400)]
Set GDB version number to 9.1.
gdb/ChangeLog:
* version.in: Set GDB version number to 9.1.
GDB Administrator [Sat, 8 Feb 2020 00:01:33 +0000 (00:01 +0000)]
Automatic date update in version.in
Iain Buclaw [Wed, 5 Feb 2020 11:45:13 +0000 (12:45 +0100)]
Make fputs_unfiltered use fputs_maybe_filtered
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 [Wed, 5 Feb 2020 11:25:09 +0000 (12:25 +0100)]
Make gdb_flush also flush the wrap buffer
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 [Wed, 5 Feb 2020 09:53:44 +0000 (10:53 +0100)]
Revert basenames_may_differ patch
Commit
a0c1ffedc 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 [Fri, 7 Feb 2020 00:01:51 +0000 (00:01 +0000)]
Automatic date update in version.in
Tony [Thu, 6 Feb 2020 19:46:19 +0000 (14:46 -0500)]
Update documentation
- Update README-ROCM.md
- Remove unnecessary @indent from gdb.texinfo copyright block
- Correct spelling mistake in gdb.texinfo
Change-Id: I56dde693570119683bfcc86d85ae8eebe522eff5
Tony [Fri, 24 Jan 2020 06:47:22 +0000 (01:47 -0500)]
Update AMD GPU chip names.
Change-Id: Id893a23603fd39ffc7972580bcc25286a7c4805d
Tony [Fri, 24 Jan 2020 06:47:22 +0000 (01:47 -0500)]
Add heterogeneous debugging support and AMD GPU information.
Change-Id: I1a7d9a3837abc48174f4da6e88ea3cdc1f918176
rohit pathania [Fri, 20 Dec 2019 11:04:04 +0000 (06:04 -0500)]
Resubmiting Tests for showing various information in hip device code
Change-Id: I33906bdcc953118bf76c37d66a9bed16886fbcb7
Laurent Morichetti [Thu, 6 Feb 2020 23:46:16 +0000 (15:46 -0800)]
Merge branch 'gdb-9-branch' into amd-staging-rocgdb-9
Change-Id: I6427b9979d8e5f92d50dd8cdefa923568a33260e
GDB Administrator [Thu, 6 Feb 2020 00:01:13 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 5 Feb 2020 00:01:15 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 4 Feb 2020 00:01:43 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 3 Feb 2020 00:01:43 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 2 Feb 2020 00:01:30 +0000 (00:01 +0000)]
Automatic date update in version.in
Sergio Durigan Junior [Sat, 1 Feb 2020 20:33:31 +0000 (15:33 -0500)]
Implement '--enable-src-release-build' option and make src-release.sh use it
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 [Sat, 1 Feb 2020 11:25:19 +0000 (15:25 +0400)]
libctf: compilation failure on MinGW due to missing errno values
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 [Sat, 1 Feb 2020 00:01:34 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 31 Jan 2020 00:01:41 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 30 Jan 2020 00:01:30 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 29 Jan 2020 00:01:22 +0000 (00:01 +0000)]
Automatic date update in version.in
Hannes Domani [Tue, 28 Jan 2020 17:24:31 +0000 (18:24 +0100)]
Fix library segment-address for 64bit values
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 [Tue, 28 Jan 2020 00:02:48 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 27 Jan 2020 00:01:57 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 26 Jan 2020 00:01:35 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 25 Jan 2020 00:00:54 +0000 (00:00 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 24 Jan 2020 00:01:02 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 23 Jan 2020 00:01:16 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 22 Jan 2020 00:01:18 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 21 Jan 2020 00:01:48 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 20 Jan 2020 00:01:02 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 19 Jan 2020 00:01:28 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 18 Jan 2020 00:01:25 +0000 (00:01 +0000)]
Automatic date update in version.in
Joel Brobecker [Fri, 17 Jan 2020 18:30:39 +0000 (19:30 +0100)]
Abort configure immediately if building GDB in tree
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 [Fri, 17 Jan 2020 00:01:31 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 16 Jan 2020 00:01:33 +0000 (00:01 +0000)]
Automatic date update in version.in
Laurent Morichetti [Wed, 15 Jan 2020 05:10:27 +0000 (21:10 -0800)]
Use malloc/free in the dbgapi callbacks
Replace xmalloc/xfree with malloc/free for the allocate_memory/
deallocate_memory callbacks. The dbgapi requires nullptr to be
returned if the memory cannot be allocated, but xmalloc throws
an internal gdb error in such cases.
gdb/ChangeLog:
* gdb/rocm-tdep.c: Adjust callbacks.
Depends-On: Id4af9dcd08b66acb6a9e9997c28a2807a5e0652e
Change-Id: I1cf6a4f6e96d8b86b716291f03a22dfbd5d83262
Laurent Morichetti [Wed, 15 Jan 2020 02:14:13 +0000 (18:14 -0800)]
Fix issues with multiple inferiors
Issue #1:
Thread 3 "bit_extract_kernel" hit Breakpoint 1, bit_extract_kernel ()
(gdb) add-inferior
[New inferior 2]
Added inferior 2 on connection 1 (native)
(gdb) info threads
amd_dbgapi_wave_list failed (rc=-14)
An inferior may not have yet been attached when update_thread_list is
called. The inferior should be skipped if its process_id is null.
Issue #2:
Thread 3 "bit_extract_kernel" hit Breakpoint 1, bit_extract_kernel ()
(gdb) add-inferior -exec /bin/ls
[New inferior 2]
Added inferior 2 on connection 1 (native)
Reading symbols from /bin/ls...
(No debugging symbols found in /bin/ls)
(gdb) inferior 2
[Switching to inferior 2 [<null>] (/bin/ls)]
(gdb) run
Starting program: /bin/ls
Warning:
Cannot insert breakpoint -8.
Cannot access memory at address 0x7fffedaa265b
Internal ROCgdbapi breakpoints should not be re-evaluated for new
inferiors. They are inserted for a specific process_id, and removed
when the process is detached.
gdb/ChangeLog:
* gdb/rocm-tdep.c: Skip inferiors without process_ids. Override
breakpoint_ops::re_set for rocm internal breakpoints to
disable re-evaluation.
Change-Id: Icb0be93b74aae1cf80c7f1657cf6d01e16eb8efb
Laurent Morichetti [Wed, 15 Jan 2020 00:22:33 +0000 (16:22 -0800)]
Fix build error in gdb/rocm-tdep.c
This patch fixes the following build error:
../../gdb/rocm-tdep.c: In function ‘void async_file_flush()’:
../../gdb/rocm-tdep.c:205:1: error: no previous declaration for ‘void async_file_flush()’ [-Werror=missing-declarations]
async_file_flush (void)
^~~~~~~~~~~~~~~~
Change-Id: Ia5be169ce25452e40eeba0b6ff29d3c07db2795c
Laurent Morichetti [Wed, 15 Jan 2020 20:44:44 +0000 (12:44 -0800)]
Merge branch 'gdb-9-branch' into amd-staging-rocgdb-9
Change-Id: I8bae375370df2248e4e9330060455f93cce3eed2
GDB Administrator [Wed, 15 Jan 2020 00:00:56 +0000 (00:00 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 14 Jan 2020 00:00:55 +0000 (00:00 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 13 Jan 2020 00:00:50 +0000 (00:00 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 12 Jan 2020 00:02:18 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 11 Jan 2020 00:01:19 +0000 (00:01 +0000)]
Automatic date update in version.in
Christian Biesinger [Wed, 18 Dec 2019 18:06:43 +0000 (12:06 -0600)]
Don't define _FORTIFY_SOURCE on MinGW
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 [Fri, 10 Jan 2020 00:00:56 +0000 (00:00 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 9 Jan 2020 00:02:08 +0000 (00:02 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 8 Jan 2020 00:00:53 +0000 (00:00 +0000)]
Automatic date update in version.in
Tom Tromey [Thu, 19 Dec 2019 18:35:22 +0000 (11:35 -0700)]
Add constructor to stap_static_probe_ops
PR build/24937 concerns an error given by the clang provided by a
particular version of macOS. In particular, it reports
error: default initialization of an object of const type 'const
stap_static_probe_ops' without a user-provided default constructor
Although (at least according to sources I found online) this was
resolved as a bug in the standard, it seemed simple enough to work
around this.
Given that this is a trivial build fix, I think it should go on the
gdb 9 branch as well.
2020-01-07 Tom Tromey <tromey@adacore.com>
PR build/24937:
* stap-probe.c (class stap_static_probe_ops): Add constructor.
Change-Id: I18f180c17850f420e9b66afc67f9cb3d8dceb0b3
GDB Administrator [Tue, 7 Jan 2020 00:00:51 +0000 (00:00 +0000)]
Automatic date update in version.in
Andrew Burgess [Thu, 26 Dec 2019 20:56:01 +0000 (20:56 +0000)]
gdb: Fix backtrace with disassemble-next-line on
In this commit:
commit
ec8e2b6d3051f0b4b2a8eee9917898e95046c62f
Date: Fri Jun 14 23:43:00 2019 +0100
gdb: Don't allow annotations to influence what else GDB prints
A change was accidentally made that moved a call to do_gdb_disassembly
out of an if block guarded by 'if (source_print && sal.symtab)'. The
result was that if a user has 'set disassemble-next-line on' then the
backtrace would now include some disassembly of a few instructions in
each frame.
This change was not intentional, but was not spotted by any tests.
This commit restores the old behaviour and adds a test to ensure this
doesn't break again in the future.
gdb/ChangeLog:
* stack.c (print_frame_info): Move disassemble_next_line code
inside source_print block.
gdb/testsuite/ChangeLog:
* gdb.base/backtrace.c: New file.
* gdb.base/backtrace.exp: New file.
Change-Id: I47c52a202fa74be138382646b695827940178689
rohit pathania [Fri, 20 Dec 2019 10:59:13 +0000 (05:59 -0500)]
modified test code from info rocm devices to info agents
Change-Id: I70c83c5cf3e1ca3b13dbd31e23cd38029f40bfd3
Laurent Morichetti [Thu, 2 Jan 2020 18:20:17 +0000 (10:20 -0800)]
Update copyright year
Change-Id: I52f92931a188148074b46e956df8f14d5b2b81e7
Laurent Morichetti [Mon, 6 Jan 2020 18:22:01 +0000 (10:22 -0800)]
Merge branch 'gdb-9-branch' into amd-staging-rocgdb-9
Change-Id: I76e59526bf7d95713536543d66356397a5737e82
GDB Administrator [Mon, 6 Jan 2020 00:01:03 +0000 (00:01 +0000)]
Automatic date update in version.in
Eli Zaretskii [Sun, 5 Jan 2020 05:50:27 +0000 (09:50 +0400)]
libctf: Add configure check for asprintf (for MinGW)
This commit fixes a compilation warning when compiling libctf
on MinGW:
libctf/ctf-dump.c:118:8: warning: implicit declaration of function
'asprintf'; did you mean 'vasprintf'? [-Wimplicit-function-declaration]
if (asprintf (&bit, " %lx: [slice 0x%x:0x%x]",
^~~~~~~~
vasprintf
MinGW doesn't provide that function, so we depend on the one provided
by libiberty. However, the declaration is guarded by HAVE_DECL_ASPRINTF,
which we do not have in libctf's config.h.
libctf/ChangeLog:
PR binutils/25155:
* configure.ac: Add AC_CHECK_DECLS([asprintf]).
* configure, config.h.in: Regenerate.
(cherry picked from commit
3a657c600bde2d3bd84870f75968622bbdb69ce8)
Joel Brobecker [Sun, 5 Jan 2020 05:49:33 +0000 (09:49 +0400)]
libctf: Regenerate Makefile.in and acinclude.m4
I noticed that if I run "autoreconf" with vanilla automake-1.15.1
and autoconf-2.69, I get some differences.
libctf/ChangeLog:
* Makefile.in, aclocal.m4: Regenerate.
Joel Brobecker [Wed, 1 Jan 2020 06:47:50 +0000 (10:47 +0400)]
Update copyright year in gdbarch.sh doc/gdb.texinfo and doc/refcard.tex
These are files that need to be updated by hand, because the copyright.py
script isn't able to handle them automatically.
gdb/ChangeLog:
* gdbarch.sh: Update copyright year range of generated files.
gdb/doc/ChangeLog:
* gdb.texinfo, refcard.tex: Update copyright year range.
(cherry picked from commit
e5d78223eaf178ebb23aa20f209f71497aaae722)
Joel Brobecker [Wed, 1 Jan 2020 06:45:00 +0000 (10:45 +0400)]
Copyright year range updates after running gdb/copyright.py
gdb/ChangeLog:
Update copyright year range in all the GDB files automatically
handled by our copyright.py script.
Joel Brobecker [Wed, 1 Jan 2020 06:32:53 +0000 (10:32 +0400)]
gdb/copyright.py: Convert to Python 3
gdb/ChangeLog:
* copyright.py: Convert to Python 3.
(cherry picked from commit
5f4def5cbd12e77075f64a6854fb002f34be8a01)
Joel Brobecker [Wed, 1 Jan 2020 06:32:30 +0000 (10:32 +0400)]
gdb/copyright.py: Adapt after move of gnulib from gdb to toplevel
gdb/ChangeLog:
* copyright.py: Adapt after move of gnulib directory from gdb
directory to toplevel directory.
(cherry picked from commit
51fd40020e1e0b21642cdec9c749f2e3862939ea)
Joel Brobecker [Wed, 1 Jan 2020 06:32:20 +0000 (10:32 +0400)]
gdb/copyright.py: Exit if run from the wrong directory
We printed an error, but kept going anyway... ;-)
gdb/ChangeLog:
* copyright.py (main): Exit if run from the wrong directory.
(cherry picked from commit
5fb651f2ddd54a1d3da6fcd172d9fab81893bbf9)
Joel Brobecker [Wed, 1 Jan 2020 06:32:04 +0000 (10:32 +0400)]
update copyright year in version output of gdb, gdbserver and gdbreplay
gdb/ChangeLog:
* top.c (print_gdb_version): Change copyright year to 2020.
gdb/gdbserver/ChangeLog:
* server.c (gdbserver_version): Change copyright year to 2020.
* gdbreplay.c (gdbreplay_version): Likewise.
(cherry picked from commit
5dd8bf886a3f7535e0ad8b5218275efcf2cfff31)
GDB Administrator [Sun, 5 Jan 2020 00:01:40 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 4 Jan 2020 00:00:48 +0000 (00:00 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 3 Jan 2020 00:01:53 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Thu, 2 Jan 2020 00:01:20 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 1 Jan 2020 00:00:50 +0000 (00:00 +0000)]
Automatic date update in version.in
Laurent Morichetti [Tue, 31 Dec 2019 14:58:47 +0000 (06:58 -0800)]
Merge branch 'gdb-9-branch' into amd-staging-rocgdb-9
Change-Id: Ide7bbea659e5594e8ae21e722840a09e4ade37db
GDB Administrator [Tue, 31 Dec 2019 00:01:13 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Mon, 30 Dec 2019 00:00:50 +0000 (00:00 +0000)]
Automatic date update in version.in
GDB Administrator [Sun, 29 Dec 2019 00:01:53 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Sat, 28 Dec 2019 00:01:17 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Fri, 27 Dec 2019 00:01:22 +0000 (00:01 +0000)]
Automatic date update in version.in
Christian Biesinger [Wed, 18 Dec 2019 21:03:07 +0000 (15:03 -0600)]
Consistently quote variables used with "test"
This ensures that empty variables and variables with spaces are handled
correctly.
Code was inconsistent on whether the constant string (e.g. yes/no)
should also be quoted; I tried to be consistent with surrounding code.
This fixes the error Eli reported during configure with mingw (though that
was not fatal).
gdb/ChangeLog:
2019-12-19 Christian Biesinger <cbiesinger@google.com>
* configure: Regenerate.
* configure.ac: Quote variable arguments of test.
* gdbsupport/common.m4: Likewise.
gdb/gdbserver/ChangeLog:
2019-12-19 Christian Biesinger <cbiesinger@google.com>
* configure: Regenerate.
* configure.ac: Quote variable arguments of test.
Change-Id: I220e78b52c7db88b9dd058eda604635b03464fac
GDB Administrator [Thu, 26 Dec 2019 00:01:40 +0000 (00:01 +0000)]
Automatic date update in version.in
GDB Administrator [Wed, 25 Dec 2019 00:00:57 +0000 (00:00 +0000)]
Automatic date update in version.in
GDB Administrator [Tue, 24 Dec 2019 00:00:56 +0000 (00:00 +0000)]
Automatic date update in version.in
Eli Zaretskii [Mon, 23 Dec 2019 14:28:32 +0000 (16:28 +0200)]
Fix compilation of Readline on mingw.org's MinGW
readline/ChangeLog
2019-12-23 Eli Zaretskii <eliz@gnu.org>
* posixstat.h (S_IRGRP, S_IWGRP, S_IXGRP, S_IROTH, S_IWOTH)
(S_IXOTH, S_IRWXG, S_IRWXO): Define if undefined, even if S_IRWXU
is defined, because non-Posix systems may defined only the user
bits.
(cherry picked from commit
e76ff636537c6140bb9d0b0a39260d840f37ca7e)
GDB Administrator [Mon, 23 Dec 2019 00:00:53 +0000 (00:00 +0000)]
Automatic date update in version.in
Laurent Morichetti [Sun, 22 Dec 2019 06:05:30 +0000 (22:05 -0800)]
Fix test failures (arch not recognized)
The following tests:
- gdb.base/all-architectures-0.exp
- gdb.base/all-architectures-1.exp
- gdb.base/all-architectures-3.exp
fail with an "arch not recognized" error.
GDB cannot select architectures that are not supported by the ROCdbgapi
library. Remove unsupported architectures from the arch_info struct.
bfd/ChangeLog:
* cpu-amdgcn.c (arch_info_struct): Remove unsupported
architectures.
Change-Id: Ie9c72499fecdd64223184864cfe425330b582cf3
This page took 0.041502 seconds and 4 git commands to generate.