From: Hui Zhu <teawater@gmail.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: Build gdbtk-cmds.c get error
Date: Mon, 05 Jul 2010 05:54:00 -0000 [thread overview]
Message-ID: <AANLkTilvRuDGmR2gZyJxGAmJk0jrSY9lm1x6Ae9O2I4F@mail.gmail.com> (raw)
In-Reply-To: <4C30CF29.7090009@redhat.com>
I am OK now. Thanks Keith.
Best regards,
Hui
On Mon, Jul 5, 2010 at 02:12, Keith Seitz <keiths@redhat.com> wrote:
> On 07/04/2010 01:20 AM, Hui Zhu wrote:
>>
>> ../../src/gdb/gdbtk/generic/gdbtk-bp.c:558: error: too many arguments
>> to function 'create_breakpoint'
>
> I've committed the attached patch to fix this, another API change in gdb.
>
> Thank you for bringing this to my attention.
>
> Keith
>
> ChangeLog
> 2010-07-04 Keith Seitz <keiths@redhat.com>
>
> * generic/gdbtk-bp.c (gdb_set_bp): Update arguments for API
> change in create_breakpoint.
>
next prev parent reply other threads:[~2010-07-05 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-04 8:20 Hui Zhu
2010-07-04 18:13 ` Keith Seitz
2010-07-05 5:54 ` Hui Zhu [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-14 9:55 Hui Zhu
2010-06-17 2:18 ` 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=AANLkTilvRuDGmR2gZyJxGAmJk0jrSY9lm1x6Ae9O2I4F@mail.gmail.com \
--to=teawater@gmail.com \
--cc=insight@sourceware.org \
--cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).