Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simark@simark.ca>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] [gdbsupport] Add gdb::{waitpid,read,write,close}
Date: Fri, 29 Nov 2024 17:23:15 +0100	[thread overview]
Message-ID: <2a0ca637-82c7-4194-9b5e-6ce6802e3415@suse.de> (raw)
In-Reply-To: <e2d73133-17df-4704-b0cd-c797571c0474@simark.ca>

On 11/29/24 17:15, Simon Marchi wrote:
> 
> 
> On 2024-11-22 11:46, Tom de Vries wrote:
>> On 11/5/24 13:07, Tom de Vries wrote:
>>> On 11/1/24 18:35, Tom Tromey wrote:
>>>>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
>>>>
>>>> Tom> +namespace gdb {
>>>> Tom> +
>>>> Tom> +extern "C" {
>>>>
>>>> I didn't even know this was valid ... but is it really needed?
>>>> It seems wrong.
>>>>
>>>
>>> It seemed to work:
>>> ...
>>> $ cat test.c
>>> namespace gdb {
>>>
>>>     extern "C" {
>>>       int foo (void) { return 1; };
>>>     }
>>> }
>>>
>>> $ cat test2.c
>>> namespace gdb {
>>>     extern "C" {
>>>       int foo (void);
>>>     }
>>> }
>>>
>>> int
>>> main (void)
>>> {
>>>     return gdb::foo ();
>>> }
>>> $ g++ test.c test2.c
>>> ...
>>> but the linkage symbol is plain foo:
>>> ...
>>> $ nm ./a.out  | grep foo
>>> 00000000004004c7 T foo
>>> ...
>>>
>>> So, you're right, this is wrong.
>>>
>>> I seem to have ended up with gdb_waitpid instead of gdb::waitpid in v2, similar to gdb_select, but thinking about it now I slightly prefer gdb::waitpid.  I suppose it doesn't matter that much.
>>>
>>
>> When looking at this again today, it bugged me enough rewrite v2 in the gdb::waitpid style.  Committed after retesting.
> 
> When building for mingw-w64, I see this, which seems related:
> 
>        CXX    cli/cli-cmds.o
>      In file included from /home/simark/src/binutils-gdb/gdb/cli/cli-cmds.c:58:
>      /home/simark/src/binutils-gdb/gdb/../gdbsupport/eintr.h: In function ‘pid_t gdb::waitpid(pid_t, int*, int)’:
>      /home/simark/src/binutils-gdb/gdb/../gdbsupport/eintr.h:77:35: error: ‘::waitpid’ has not been declared; did you mean ‘gdb::waitpid’?
>         77 |   return gdb::handle_eintr (-1, ::waitpid, pid, wstatus, options);
>            |                                   ^~~~~~~
>            |                                   gdb::waitpid
>      /home/simark/src/binutils-gdb/gdb/../gdbsupport/eintr.h:75:1: note: ‘gdb::waitpid’ declared here
>         75 | waitpid (pid_t pid, int *wstatus, int options)
>            | ^~~~~~~
> 
> Note that to get to it, you have to step past this other build error in
> gdbserver (by doing `make all-gdb` for instance):
> 
>    https://inbox.sourceware.org/gdb-patches/75926446-4c8a-40ee-8ed8-ab55f38e1520@simark.ca/T/#m194744b18419e37dfb4ec82c8e0ce73fb017ba17

Hi Simon,

thanks for reporting this.

I don't have a windows setup unfortunately, so I have no way of 
reproducing this, and at this point I have no idea why waitpid is not 
declared.

Thanks,
- Tom

  reply	other threads:[~2024-11-29 16:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 17:49 Tom de Vries
2024-10-28 17:49 ` [PATCH 2/3] [gdb] Use gdb::waitpid more often Tom de Vries
2024-10-28 17:49 ` [PATCH 3/3] [gdbsupport] Add gdb::wait Tom de Vries
2024-11-01 17:35 ` [PATCH 1/3] [gdbsupport] Add gdb::{waitpid,read,write,close} Tom Tromey
2024-11-05 12:07   ` Tom de Vries
2024-11-22 16:46     ` Tom de Vries
2024-11-29 16:15       ` Simon Marchi
2024-11-29 16:23         ` Tom de Vries [this message]
2024-11-29 16:27           ` Simon Marchi
2024-11-29 16:32             ` Tom de Vries
2024-11-29 17:23               ` Simon Marchi
2024-11-29 17:28                 ` Tom de Vries
2024-12-02  9:38           ` Kévin Le Gouguec
2024-12-02 11:07             ` Tom de Vries

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=2a0ca637-82c7-4194-9b5e-6ce6802e3415@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --cc=tom@tromey.com \
    /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