From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/python] Fix cpychecker error in recpy_bt_goto
Date: Thu, 04 Oct 2018 22:12:00 -0000 [thread overview]
Message-ID: <87h8i1icpu.fsf@tromey.com> (raw)
In-Reply-To: <20181004180759.GA23984@delia> (Tom de Vries's message of "Thu, 4 Oct 2018 20:08:00 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> When using cpychecker, we run into this error:
Thanks for trying this out!
Tom> 2018-10-04 Tom de Vries <tdevries@suse.de>
Tom> * python/py-record-btrace.c (recpy_bt_goto): Fix type mismatch in
Tom> PyArg_ParseTuple call.
Tom> + obj = (const recpy_element_object *)parse_obj;
There should be a space after the close paren.
Ok with that change.
Tom
prev parent reply other threads:[~2018-10-04 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 18:08 Tom de Vries
2018-10-04 22:12 ` Tom Tromey [this message]
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=87h8i1icpu.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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