public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Rainer Orth <ro@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb/gdb-12-branch] Fix procfs.c compilation
Date: Thu, 31 Mar 2022 08:38:20 +0000 (GMT)	[thread overview]
Message-ID: <20220331083820.803663853809@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=09ab0d2eecfbcb5ac68617fd356c9f8067b07769

commit 09ab0d2eecfbcb5ac68617fd356c9f8067b07769
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date:   Thu Mar 31 10:38:01 2022 +0200

    Fix procfs.c compilation
    
    procfs.c doesn't compile on Solaris:
    
    /vol/src/gnu/gdb/hg/master/local/gdb/procfs.c: In member function ‘virtual bool procfs_target::info_proc(const char*, info_proc_what)’:
    /vol/src/gnu/gdb/hg/master/local/gdb/procfs.c:3302:3: error: ‘gdb_argv’ was not declared in this scope
     3302 |   gdb_argv built_argv (args);
          |   ^~~~~~~~
    /vol/src/gnu/gdb/hg/master/local/gdb/procfs.c:3303:20: error: ‘built_argv’ was not declared in this scope; did you mean ‘buildargv’?
     3303 |   for (char *arg : built_argv)
          |                    ^~~~~~~~~~
          |                    buildargv
    
    Fixed by including  "gdbsupport/buildargv.h".
    
    Tested on amd64-pc-solaris2.11, sparcv9-sun-solaris2.11.

Diff:
---
 gdb/procfs.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gdb/procfs.c b/gdb/procfs.c
index 840201d1897..6b269b658e2 100644
--- a/gdb/procfs.c
+++ b/gdb/procfs.c
@@ -45,6 +45,7 @@
 #include "observable.h"
 #include "gdbsupport/scoped_fd.h"
 #include "gdbsupport/pathstuff.h"
+#include "gdbsupport/buildargv.h"
 
 /* This module provides the interface between GDB and the
    /proc file system, which is used on many versions of Unix


                 reply	other threads:[~2022-03-31  8:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220331083820.803663853809@sourceware.org \
    --to=ro@sourceware.org \
    --cc=gdb-cvs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).