From: Will Senn <will.senn@gmail.com>
To: Bakul Shah <bakul@bitblocks.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] wump.c for v6
Date: Mon, 6 Jan 2020 14:29:22 -0600 [thread overview]
Message-ID: <46eb816b-3faa-b12a-a67c-e5aa84983158@gmail.com> (raw)
In-Reply-To: <20200106191033.82856156E42D@mail.bitblocks.com>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
On 1/6/20 1:10 PM, Bakul Shah wrote:
> On Mon, 06 Jan 2020 12:38:25 -0600 Will Senn <will.senn@gmail.com> wrote:
>> On 1/6/20 12:29 PM, Warner Losh wrote:
>>> The good news is that disassembly will tell you right away if it was
>>> written in C or not.
>>>
>>>
>> OK. I give up. How?
> Running strings on the wump binary in Dennis_v6 and comparing
> its output with actual strings in the wump.c source n
> Henry_Spencerv7 reveals they are pretty much the same.
Oh. That's funny. I tried strings in v6, it wasn't there. It didn't
occur to me to do it in MacOS...
--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
[-- Attachment #2: Type: text/html, Size: 1449 bytes --]
next prev parent reply other threads:[~2020-01-06 20:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 6:13 Will Senn
2020-01-06 15:20 ` Clem Cole
2020-01-06 15:24 ` Clem Cole
2020-01-06 16:25 ` Will Senn
2020-01-06 16:35 ` Clem Cole
2020-01-06 18:29 ` Warner Losh
2020-01-06 18:38 ` Will Senn
2020-01-06 18:48 ` Warner Losh
2020-01-06 21:08 ` Clem Cole
2020-01-06 21:38 ` Clem Cole
2020-01-06 22:14 ` Warner Losh
2020-01-06 23:46 ` Will Senn
2020-01-07 20:04 ` Sean Dwyer via TUHS
2020-01-07 21:08 ` Clem Cole
2020-01-08 6:35 ` Sean Dwyer via TUHS
2020-01-06 19:10 ` Bakul Shah
2020-01-06 20:29 ` Will Senn [this message]
2020-01-07 0:40 Noel Chiappa
2020-01-07 0:44 ` Warner Losh
2020-01-07 1:58 Noel Chiappa
2020-01-10 14:27 Noel Chiappa
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=46eb816b-3faa-b12a-a67c-e5aa84983158@gmail.com \
--to=will.senn@gmail.com \
--cc=bakul@bitblocks.com \
--cc=tuhs@minnie.tuhs.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).