public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] Fix return type typo in obsd-nat.c that breaks build on OpenBSD
@ 2019-07-26 21:05 Tom Tromey
0 siblings, 0 replies; only message in thread
From: Tom Tromey @ 2019-07-26 21:05 UTC (permalink / raw)
To: gdb-cvs
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=89b085acaf8d449d6c9c0b0490c6a0c9a745db5d
commit 89b085acaf8d449d6c9c0b0490c6a0c9a745db5d
Author: Brian Callahan <callab5@rpi.edu>
Date: Fri Jul 26 14:48:15 2019 -0400
Fix return type typo in obsd-nat.c that breaks build on OpenBSD
To recap the bug report:
Commit a068643 introduced a small typo that breaks the gdb build on OpenBSD.
Line 38 of obsd-nat.c needs to be changed from std::sring to std::string.
gdb/ChangeLog
2019-07-26 Brian Callahan <bcallah@openbsd.org>
PR gdb/24839:
* gdb/obsd-nat.c (obsd_nat_target::pid_to_str): Fix typo in return
type.
Diff:
---
gdb/ChangeLog | 6 ++++++
gdb/obsd-nat.c | 2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index a1d39b9..7a01b8f 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,9 @@
+2019-07-26 Brian Callahan <bcallah@openbsd.org>
+
+ PR gdb/24839:
+ * gdb/obsd-nat.c (obsd_nat_target::pid_to_str): Fix typo in return
+ type.
+
2019-07-25 Christian Biesinger <cbiesinger@google.com>
* python/py-objfile.c (add_separate_debug_file): Fix comment about
diff --git a/gdb/obsd-nat.c b/gdb/obsd-nat.c
index 88c01df..0351f69 100644
--- a/gdb/obsd-nat.c
+++ b/gdb/obsd-nat.c
@@ -35,7 +35,7 @@
#ifdef PT_GET_THREAD_FIRST
-std::sring
+std::string
obsd_nat_target::pid_to_str (ptid_t ptid)
{
if (ptid.lwp () != 0)
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-07-26 21:05 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-26 21:05 [binutils-gdb] Fix return type typo in obsd-nat.c that breaks build on OpenBSD Tom Tromey
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).