From: Joel Brobecker <brobecker@adacore.com>
To: Alberto Luaces <aluaces@udc.es>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Undefined uintptr_t with mingw
Date: Wed, 22 Dec 2010 04:00:00 -0000 [thread overview]
Message-ID: <20101222040005.GG2596@adacore.com> (raw)
In-Reply-To: <87k4j3krv3.fsf@eps142.cdf.udc.es>
[I changed the subject to include "gdbserver" in the subject]
> diff -ur gdb-7.2orig/gdb/gdbserver/win32-low.c gdb-7.2/gdb/gdbserver/win32-low.c
> --- gdb-7.2orig/gdb/gdbserver/win32-low.c 2010-12-21 16:27:10.000000000 +0100
> +++ gdb-7.2/gdb/gdbserver/win32-low.c 2010-12-21 17:21:56.000000000 +0100
> @@ -33,6 +33,7 @@
> #include <sys/param.h>
> #include <malloc.h>
> #include <process.h>
> +#include <stdint.h>
Pedro is the current expert for gdbserver, so please wait for his
review, but I'm thinking that we should probably do the same as GDB,
which is include stdlib in the gdbserver equivalent of defs.h (i.e.
server.h).
--
Joel
next prev parent reply other threads:[~2010-12-22 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 16:35 Alberto Luaces
2010-12-22 4:00 ` Joel Brobecker [this message]
2010-12-22 12:29 ` Pedro Alves
2010-12-22 13:11 ` Pedro Alves
2010-12-22 14:32 ` Joel Brobecker
2010-12-22 13:12 ` Joel Brobecker
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=20101222040005.GG2596@adacore.com \
--to=brobecker@adacore.com \
--cc=aluaces@udc.es \
--cc=gdb-patches@sources.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