Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Stan Cox <scox@redhat.com>
Cc: Pedro Alves <palves@redhat.com>,  gdb-patches@sourceware.org
Subject: Re: [RFC][PATCH v3] Consolidate gdbserver global variables
Date: Fri, 08 Jun 2018 16:11:00 -0000	[thread overview]
Message-ID: <87po11l0lw.fsf@tromey.com> (raw)
In-Reply-To: <9e844707-a2f8-c969-4d09-7ee2fa3bd1ed@redhat.com> (Stan Cox's	message of "Tue, 8 May 2018 16:58:34 -0400")

>>>>> "Stan" == Stan Cox <scox@redhat.com> writes:

Stan>     * server.h (struct client_state): New.
Stan>     * server.c (cont_thread, general_thread, multi_process)
Stan>     (report_fork_events, report_vfork_events, report_exec_events)
Stan>     (report_thread_events, swbreak_feature, hwbreak_feature)
Stan>     (vCont_supported, disable_randomization, pass_signals)
Stan>     (program_signals, program_signals_p, last_status, last_ptid, own_buf):
Stan>     Moved to client_state.
Stan>     * remote-utils.c (remote_debug, noack_mode)
Stan>     (transport_is_reliable): Moved to client_state.
Stan>     * tracepoint.c (current_traceframe): Moved to client_state.

I think this broke the mingw build.

I configured with:

../binutils-gdb/configure --disable-{binutils,gas,gold,gprof,ld,sim} \
  --host i686-w64-mingw32 --target i686-w64-mingw32

Then building:

../../../binutils-gdb/gdb/gdbserver/win32-low.c: In function 'int win32_create_inferior(const char*, const std::vector<char*>&)':
../../../binutils-gdb/gdb/gdbserver/win32-low.c:709:3: error: 'last_ptid' was not declared in this scope
   last_ptid = win32_wait (pid_to_ptid (current_process_id), &last_status, 0);
   ^~~~~~~~~
../../../binutils-gdb/gdb/gdbserver/win32-low.c:709:3: note: suggested alternative: 'last_sig'
   last_ptid = win32_wait (pid_to_ptid (current_process_id), &last_status, 0);
   ^~~~~~~~~
   last_sig
../../../binutils-gdb/gdb/gdbserver/win32-low.c:709:62: error: 'last_status' was not declared in this scope
   last_ptid = win32_wait (pid_to_ptid (current_process_id), &last_status, 0);
                                                              ^~~~~~~~~~~
../../../binutils-gdb/gdb/gdbserver/win32-low.c:709:62: note: suggested alternative: 'cached_status'
   last_ptid = win32_wait (pid_to_ptid (current_process_id), &last_status, 0);
                                                              ^~~~~~~~~~~
                                                              cached_status

thanks,
Tom


  parent reply	other threads:[~2018-06-08 16:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 22:03 [RFC][PATCH] " Stan Cox
2018-01-31  3:41 ` Stan Cox
2018-04-23 17:58   ` Pedro Alves
2018-05-03 15:06     ` [RFC][PATCH v2] " Stan Cox
2018-05-04 14:14       ` Pedro Alves
2018-05-07 19:17         ` Frank Ch. Eigler
2018-05-25 14:31           ` Pedro Alves
2018-05-08 20:58         ` [RFC][PATCH v3] " Stan Cox
2018-05-25 15:01           ` Pedro Alves
2018-05-29 20:46             ` Stan Cox
2018-05-30 14:30               ` Pedro Alves
2018-06-08 16:11           ` Tom Tromey [this message]
2018-06-08 16:46             ` Stan Cox
2018-06-08 16:52               ` Tom Tromey
2018-07-10  1:14           ` Sergio Durigan Junior

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=87po11l0lw.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=scox@redhat.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