From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH 0/4] tracetool: show trace-events filename/lineno in fmt string errors
Date: Tue, 8 Dec 2020 14:20:12 +0000 [thread overview]
Message-ID: <20201208142012.GC272246@stefanha-x1.localdomain> (raw)
In-Reply-To: <20200827142915.108730-1-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On Thu, Aug 27, 2020 at 03:29:11PM +0100, Stefan Hajnoczi wrote:
> This patch series improves format string compiler error messages. Instead of
> showing the generated file, show the trace-events file where the format string
> is defined.
>
> Stefan Hajnoczi (4):
> tracetool: add output filename command-line argument
> tracetool: add out_lineno and out_next_lineno to out()
> tracetool: add input filename and line number to Event
> tracetool: show trace-events filename/lineno in fmt string errors
>
> docs/devel/tracing.txt | 3 +-
> meson.build | 3 +-
> scripts/tracetool.py | 12 ++++---
> scripts/tracetool/__init__.py | 53 +++++++++++++++++++++++++----
> scripts/tracetool/backend/ftrace.py | 4 +++
> scripts/tracetool/backend/log.py | 4 +++
> scripts/tracetool/backend/syslog.py | 4 +++
> trace/meson.build | 23 +++++--------
> 8 files changed, 76 insertions(+), 30 deletions(-)
>
> --
> 2.26.2
>
Thanks, applied to my tracing-next tree:
https://gitlab.com/stefanha/qemu/commits/tracing-next
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-12-08 14:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 14:29 [PATCH 0/4] tracetool: show trace-events filename/lineno in fmt string errors Stefan Hajnoczi
2020-08-27 14:29 ` [PATCH 1/4] tracetool: add output filename command-line argument Stefan Hajnoczi
2020-08-31 20:17 ` Philippe Mathieu-Daudé
2020-09-01 12:55 ` Peter Maydell
2020-08-27 14:29 ` [PATCH 2/4] tracetool: add out_lineno and out_next_lineno to out() Stefan Hajnoczi
2020-09-01 12:49 ` Peter Maydell
2020-08-27 14:29 ` [PATCH 3/4] tracetool: add input filename and line number to Event Stefan Hajnoczi
2020-08-31 20:20 ` Philippe Mathieu-Daudé
2020-09-01 12:50 ` Peter Maydell
2020-08-27 14:29 ` [PATCH 4/4] tracetool: show trace-events filename/lineno in fmt string errors Stefan Hajnoczi
2020-08-27 14:59 ` Peter Maydell
2020-08-28 15:36 ` Stefan Hajnoczi
2020-09-01 12:52 ` Peter Maydell
2020-12-08 14:20 ` Stefan Hajnoczi [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=20201208142012.GC272246@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).