From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Hui Zhu'" <teawater@gmail.com>
Cc: <gdb-patches@sourceware.org>,
"'Michael Snyder'" <msnyder@vmware.com>,
"'Pedro Alves'" <pedro@codesourcery.com>
Subject: RE: Process record and replay checked in to main trunk
Date: Fri, 08 May 2009 12:11:00 -0000 [thread overview]
Message-ID: <003201c9cfd6$0d96d6f0$28c484d0$@u-strasbg.fr> (raw)
In-Reply-To: <daef60380905072211p3fbd2591j8e12041ed96c452@mail.gmail.com>
I tested this both in 32bit and 64bit CORE_ADDR length.
I can confirm that cygwin compilation is fixed in both
cases with that patch and hope it will be approved
rapidly.
Thanks, Hui.
Pierre Muller
Pascal language support maintainer for GDB
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Hui Zhu
> Envoyé : Friday, May 08, 2009 7:12 AM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org; Michael Snyder; Pedro Alves
> Objet : Re: Process record and replay checked in to main trunk
>
> Hi Pierre,
>
> I make a patch to fix this bug, but I don't have cygwin.
>
> Could you please help me test this patch in cygwin?
>
> Thanks,
> Hui
>
> On Fri, May 8, 2009 at 07:06, Pedro Alves <pedro@codesourcery.com>
> wrote:
> > On Thursday 07 May 2009 23:43:13, Michael Snyder wrote:
> >> Guessing it isn't implemented for 64 bit.
> >
> > I don't think that's the problem here. Cygwin is 32-bit, and has
> > 32-bit ints.
> >
> >> ../../purecvs/gdb/linux-record.c:397: warning: unsigned int format,
> >> uint32_t arg
> >
> >> ../../purecvs/gdb/linux-record.c:629: warning: int format, uint32_t
> >> arg (arg
> >
> > Better use casts, or use plongest/pulongest/hex_string where
> appropriate?
> >
> >> Perhaps we should have a --disable-process-record config option?
> >> If only for a back-up plan?
> >
> > I think that would be more work than fixing this properly. :-)
> >
> >> ../../purecvs/gdb/linux-record.c:1636: error: `F_GETLK64' undeclared
> >> (first use in this function)
> >
> > There are a bunch of RECORD_* macros defined on top of linux-record.c
> > to replace contants like these. E.g., RECORD_Q_GETFMT. Looks like
> > this case was just missed.
> >
> > --
> > Pedro Alves
> >
next prev parent reply other threads:[~2009-05-08 12:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 7:59 Hui Zhu
2009-04-30 14:43 ` Marc Khouzam
2009-04-30 20:00 ` Michael Snyder
2009-05-01 9:16 ` Eli Zaretskii
2009-05-01 17:02 ` Hui Zhu
2009-05-01 17:55 ` Eli Zaretskii
2009-05-03 14:15 ` Hui Zhu
2009-05-04 11:17 ` Eli Zaretskii
2009-05-04 16:46 ` Michael Snyder
2009-05-05 13:48 ` Hui Zhu
2009-05-04 14:32 ` Marc Khouzam
2009-05-04 16:46 ` Eli Zaretskii
2009-05-05 14:11 ` Hui Zhu
2009-05-01 9:26 ` Eli Zaretskii
2009-05-01 17:08 ` Hui Zhu
2009-05-01 17:58 ` Eli Zaretskii
2009-05-01 13:28 ` Eli Zaretskii
2009-05-03 13:54 ` Hui Zhu
2009-05-04 11:15 ` Eli Zaretskii
2009-05-05 13:40 ` Hui Zhu
2009-05-05 19:01 ` Eli Zaretskii
2009-05-05 19:32 ` Mark Kettenis
2009-05-05 19:52 ` Eli Zaretskii
2009-05-06 13:34 ` Hui Zhu
[not found] ` <daef60380904300102o4470ac45he41f6b72176b1947@mail.gmail.com>
2009-05-07 22:24 ` Pierre Muller
2009-05-07 22:52 ` Michael Snyder
2009-05-07 23:05 ` Pedro Alves
2009-05-08 5:12 ` Hui Zhu
2009-05-08 12:11 ` Pierre Muller [this message]
2009-05-10 17:28 ` Hui Zhu
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='003201c9cfd6$0d96d6f0$28c484d0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.com \
--cc=teawater@gmail.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