From: quanstro@quanstro.net (erik quanstrom)
Subject: [9fans] libmach x86 botch
Date: Sun, 4 Sep 2011 14:36:35 -0400 [thread overview]
Message-ID: <7983be554dbf970b94efc5f54c06b4fa@ladd.quanstro.net> (raw)
In-Reply-To: <CADSkJJUnyBgoCt7bek6482BJ2SZ7vh=DbaFwNLNcY36qj994+g@mail.gmail.c>
On Sun Sep 4 14:34:41 EDT 2011, rsc at swtch.com wrote:
> asm(stackaddress) is bogus not because of libmach
> but because asm is defined to disassemble from the
> text file, not from memory. Run 'whatis asm' in acid and
> notice that it says @addr++ not *addr++.
clearly. but that's not what i'm complaining about.
i'm complaining that asm(stackaddress) accesses uninitialized
memory when printing out the error, which is therefore
exceptionally misleading.
- erik
prev parent reply other threads:[~2011-09-04 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 17:33 erik quanstrom
2011-09-04 17:38 ` erik quanstrom
2011-09-04 18:32 ` Russ Cox
[not found] ` <CADSkJJUnyBgoCt7bek6482BJ2SZ7vh=DbaFwNLNcY36qj994+g@mail.gmail.c>
2011-09-04 18:36 ` erik quanstrom [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=7983be554dbf970b94efc5f54c06b4fa@ladd.quanstro.net \
--to=quanstro@quanstro.net \
/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).