qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: Brad Campbell <brad@wasp.net.au>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Funny Bash Script ...
Date: Sun, 13 Feb 2005 16:44:57 +0100	[thread overview]
Message-ID: <20050213154457.GA16486@mail.13thfloor.at> (raw)
In-Reply-To: <420F0871.10706@wasp.net.au>

On Sun, Feb 13, 2005 at 11:57:37AM +0400, Brad Campbell wrote:
> Herbert Poetzl wrote:
> >Hi Folks!
> >
> >there is a funny bash script available at
> >
> >  http://vserver.13thfloor.at/Stuff/QEMU/rev_01.sh
> >
> >using this on object files (like the kqemu-mod-i386.o)
> >produces interesting output, which will compile nicely
> >with gcc to something very similar of the original ..
> 
> Anyone can disassemble a binary and re-compile it. 

sure, that's why this script is there ... ;)

> Understanding exactly how it works is another story entirely. 

agreed, but understanding binary code is harder ;)

> I believe you would be in violation of the license if you 
> distributed the de-compiled source, so what do you gain by 
> doing this?

well, I'm pretty sure that most of the current qemu
hackers are able to _understand_ readable assembler
code, so it might not be that complicated ...

> In addition, we are talking kernel code here. 

yes, I'm aware of that, but let me assure you, this
kernel code is much simpler than most of the userspace
part qemu folks are working with/on ...

> The sort of stuff where random compiler optimisations can cause 
> catastrophic failures. 

of course, and some hackers have been eaten by a grue!

> Can you guarantee by doing this you are generating exactly the 
> same code as you started with? 

nobody wants to do that, otherwise you could take the
object file and be done, nevertheless, comparing the
disassembled code of two object files usually sheds
some light on the differences (i.e. with diff)

> I would certainly be loathe to trust the compiled binary.

but an unknown, proprietary object file nobody takes
liability for you trust ... i.c. 

best,
Herbert

> Brad
> -- 
> "Human beings, who are almost unique in having the ability
> to learn from the experience of others, are also remarkable
> for their apparent disinclination to do so." -- Douglas Adams
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

  reply	other threads:[~2005-02-13 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-13  7:21 [Qemu-devel] Funny Bash Script Herbert Poetzl
2005-02-13  7:57 ` Brad Campbell
2005-02-13 15:44   ` Herbert Poetzl [this message]
2005-02-13  8:23 ` Grzegorz Kulewski
2005-02-13 17:06 ` Jim C. Brown

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=20050213154457.GA16486@mail.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=brad@wasp.net.au \
    --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).