From: "Andreas Färber" <andreas.faerber@web.de>
To: Lee Essen <lee.essen@nowonline.co.uk>
Cc: Blue Swirl <blauwirbel@gmail.com>,
qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] fix incorrect bracket in tracetool
Date: Fri, 16 Mar 2012 14:21:35 +0100 [thread overview]
Message-ID: <4F633E5F.1000707@web.de> (raw)
In-Reply-To: <1EA6E838-00B8-45F3-A293-BF495BF07F7B@nowonline.co.uk>
Am 16.03.2012 14:00, schrieb Lee Essen:
> On 16 Mar 2012, at 12:44, Andreas Färber wrote:
>
>> Am 16.03.2012 13:29, schrieb Lee Essen:
>>> Signed-off-by: Lee Essen <lee.essen@nowonline.co.uk>
>>>
>>> ---
>>>
>>> scripts/tracetool | 2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/scripts/tracetool b/scripts/tracetool
>>> index 65bd0a1..2e43d05 100755
>>> --- a/scripts/tracetool
>>> +++ b/scripts/tracetool
>>> @@ -123,7 +123,7 @@ get_argc()
>>> # Get the format string including double quotes for a trace event
>>> get_fmt()
>>> {
>>> - puts "${1#*)}"
>>> + puts "${1#*}"
>>> }
>>>
>>> linetoh_begin_nop()
>>>
>> Cc'ing the trace maintainer. I assume Lee forgot to look up the
>> maintainer, but Stefan, my checking MAINTAINERS indicates tracetool is
>> missing in the Tracing section too. Could you add it please?
>>
>> Not being a shell expert I can't judge what this is actually trying to
>> do. Note that there is also an effort underway to rewrite tracetool as
>> tracetool.py.
>
> Actually, I think I need to slow down a bit…
:) No need to rush, it's been broken for a while.
> there are more problems than just that bracket…
>
> # make
> GEN trace.h
> /tmp/patch/qemu/scripts/tracetool[520]: local: not found [No such file or directory]
> /tmp/patch/qemu/scripts/tracetool[66]: local: not found [No such file or directory]
> /tmp/patch/qemu/scripts/tracetool[136]: local: not found [No such file or directory]
> /tmp/patch/qemu/scripts/tracetool[55]: local: not found [No such file or directory]
> /tmp/patch/qemu/scripts/tracetool[80]: local: not found [No such file or directory]
> /tmp/patch/qemu/scripts/tracetool[55]: local: not found [No such file or directory]
>
> From what I can see "local" isn't supported in posix ...
> "The POSIX standard supports functions, as shown above, but the semantics are weaker: functions do not have local traps or options, it is not possible to define local variables, and functions can't be exported."
Hm, Blue's patch in the bug I referenced earlier still had local in it
and according to my comments worked with Solaris 10's /usr/xpg4/bin/sh,
and I don't have that issue on OpenIndiana (bash). What shell did you
test with on SmartOS?
> So I could do with some advice now on how to proceed … is the goal to keep posix shell compliance? Wait for a tracetool.py version? Or should I go back to messing with SHELL?
I'd recommend to evaluate what needs to be done to make the script(s)
POSIX-compliant. If the resulting patch is reasonable then IMO we should
apply it even if it gets replaced by a Python version later (it was
still feature-incomplete last time posted and has been floating around a
while already). Was just pointing it out for you in case it's easier to
get running on your system.
Andreas
next prev parent reply other threads:[~2012-03-16 13:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 12:29 [Qemu-devel] [PATCH] fix incorrect bracket in tracetool Lee Essen
2012-03-16 12:44 ` Andreas Färber
2012-03-16 13:00 ` Lee Essen
2012-03-16 13:19 ` Paolo Bonzini
2012-03-16 13:28 ` Andreas Färber
2012-03-16 13:21 ` Andreas Färber [this message]
2012-03-16 13:18 ` Paolo Bonzini
2012-03-16 14:56 ` Eric Blake
2012-03-19 11:59 ` Stefan Hajnoczi
2012-03-19 12:05 ` Lee Essen
2012-03-19 12:32 ` Stefan Hajnoczi
2012-03-19 12:32 ` Andreas Färber
2012-03-19 13:35 ` Lee Essen
2012-03-20 16:59 ` Stefan Hajnoczi
2012-03-20 17:11 ` Lee Essen
2012-03-21 9:52 ` Stefan Hajnoczi
2012-03-19 12:40 ` Stefan Weil
2012-03-19 12:49 ` Andreas Färber
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=4F633E5F.1000707@web.de \
--to=andreas.faerber@web.de \
--cc=blauwirbel@gmail.com \
--cc=lee.essen@nowonline.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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 NNTP newsgroup(s).