Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org, aburgess@redhat.com
Subject: Re: [PATCH] Fix procfs.c compilation on Solaris
Date: Fri, 14 Aug 2026 14:33:53 +0300	[thread overview]
Message-ID: <86lda97x7i.fsf@gnu.org> (raw)
In-Reply-To: <yddpkzlnizt.fsf@CeBiTec.Uni-Bielefeld.DE> (message from Rainer Orth on Fri, 14 Aug 2026 11:34:14 +0200)

> From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
> Cc: Andrew Burgess <aburgess@redhat.com>
> Date: Fri, 14 Aug 2026 11:34:14 +0200
> 
> procfs.c doesn't compile on trunk and the gdb-18 branch:
> 
> procfs.c: In function ‘int procfs_notice_thread(procinfo*, procinfo*, void*)’:
> procfs.c:2857:33: error: invalid use of non-static member function ‘thread_state thread_info::state() const’
>  2857 |   if (thr == NULL || thr->state == THREAD_EXITED)
>       |                      ~~~~~~~~~~~^~~~~~~~~~~~~~~~
> 
> Fixed by calling the member function.
> 
> procfs.c: In function ‘bool find_memory_regions_callback(prmap*, find_memory_region_ftype)’:
> procfs.c:3152:15: error: no match for call to ‘(find_memory_region_ftype {aka gdb::function_view<bool(long unsigned int, long unsigned int, bool, bool, bool, bool, bool, bool)>}) (CORE_ADDR, std::size_t&, bool, bool, bool, bool, bool)’
>  3152 |   return func ((CORE_ADDR) map->pr_vaddr,
>       |          ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~
>  3153 |                map->pr_size,
>       |                ~~~~~~~~~~~~~
>  3154 |                (map->pr_mflags & MA_READ) != 0,
>       |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  3155 |                (map->pr_mflags & MA_WRITE) != 0,
>       |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  3156 |                (map->pr_mflags & MA_EXEC) != 0,
>       |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  3157 |                true, /* MODIFIED is unknown, pass it as true.  */
>       |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  3158 |                false);
>       |                ~~~~~~
> 
> Fixed by passing the new HOLE arg.
> 
> procfs.c: In function ‘void info_proc_mappings(procinfo*, int)’:
> procfs.c:3257:25: error: too many arguments to function ‘bool iterate_over_mappings(procinfo*, find_memory_region_ftype, bool (*)(prmap*, find_memory_region_ftype))’
>  3257 |   iterate_over_mappings (pi, NULL, NULL, info_mappings_callback);
>       |   ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> Fixed by removing the unused arg.
> 
> Tested on sparcv9-sun-solaris2.11 and amd64-pc-solaris2.11 with results
> similar to the gdb-17 ones.
> 
> Committed to trunk.
> 
> 
> This patch should also go to the gdb-18 branch: I'm not sure if I should
> just commit it or it needs approval.

The rule until now was that each bugfix on the release branch needs a
Bugzilla report.

Thanks.

  reply	other threads:[~2026-08-14 11:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  9:34 Rainer Orth
2026-08-14 11:33 ` Eli Zaretskii [this message]
2026-08-14 11:49   ` Hannes Domani
2026-08-19 15:39     ` Andrew Burgess
2026-08-19 17:27       ` Rainer Orth

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=86lda97x7i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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