From: Frank Kotler on
NathanCBaker(a)gmail.com wrote:
> On Aug 13, 2:52 am, Willow <wrschlan...(a)gmail.com> wrote:
>> The next release will incorporate this change, but I don't want to
>> post it just yet because you built it on Linux and I want the next
>> release to be more Linux friendly! Did you have to make any changes
>> when you built it on Linux? Do you know how to make a Makefile for
>> such a complex project? The problem is there's lots of directories and
>> also there's some automatically generated code... any help on making a
>> makefile would be appreciated.
>>
>
> The only thing I did was write two small bash scripts (one for each
> subdirectory). But here is a quickly-cobbled-together, un-tested,
> simple Makefile that "might" do the job:
>
> --------8<--------
> crudasm1: crudasm1.cpp
> gcc -c -o ../x86c/x86c_insn_names.o ../x86c/x86c_insn_names.c
> gcc -c -o ../x86c/x86c_insn_name_search_table.o ../x86c/
> x86c_insn_name_search_table.c
> gcc -c -o ../x86c/x86c_insns.o ../x86c/x86c_insns.c
> gcc -c -o ../x86c/x86c_encodings.o ../x86c/x86c_encodings.c
> gcc -c -o ../x86c/x86c_decoder_table.o ../x86c/x86c_decoder_table.c
> gcc -c -o ../x86c/decode.o ../x86c/decode.c
> g++ -c -o asmwriter.o asmwriter.cpp
> g++ -o crudasm1 crudasm1.cpp asmwriter.o ../x86c/decode.o ../x86c/
> x86c_*.o
>
> clean:
> rm *.o
> rm ../x86c/*.o
>
> remove:
> rm crudasm1
> -------->8--------
>
> I will test it tomorrow.

Jeez, you're gettin' good at this, Nathan! You too, Willow! Sure enough,
once I unwrapped the fine work of my newsreader, it built without
complaint, and disassembles files!

> ...or maybe someone here will script you a
> better one if they aren't too busy testing the latest "Stdlib duo"
> powered .net assembler.

"Stdlib duo" :) :) :) I like it!

If/when I get out of the "lazy hole" I've been in lately (worse than
usual!), I'll try "crudasm1" on something more "challenging", but it
"seems to work" fine! Also gotta get back to Herbert on a couple of
things... and Japheth... So many bits, so little amBITion!

Best,
Frank
From: Karel Lejska on
On Aug 13, 8:03 am, "Dave -Turner" <ad...(a)127.0.0.1> wrote:
> >http://ref.x86asm.net/x86reference.xml
>
> XML Parsing Error: undefined entity
> Location:http://ref.x86asm.net/x86reference.xml
> Line Number 59, Column 15:        <note>&add;</note>
> --------------^

Hello Dave, don't try to display the XML using internet browser.
Nowadays browsers are not supposed to read XMLs and DTDs properly.
Download the file and open it in a decent reader/editor instead.
From: NathanCBaker on
On Aug 13, 8:38 am, Frank Kotler <fbkot...(a)verizon.net> wrote:
>
> Jeez, you're gettin' good at this, Nathan! You too, Willow! Sure enough,

Well, better would be something like what is at the bottom of this
page:

http://mrbook.org/tutorials/make/

We will need to start it like this:

CCPP=g++
CC=gcc

> once I unwrapped the fine work of my newsreader, it built without
> complaint, and disassembles files!
>
> > ...or maybe someone here will script you a
> > better one if they aren't too busy testing the latest "Stdlib duo"
> > powered .net assembler.
>
> "Stdlib duo" :) :) :) I like it!
>
> If/when I get out of the "lazy hole" I've been in lately (worse than
> usual!), I'll try "crudasm1" on something more "challenging", but it

I think that Wolfgang's 'disass.com' might contain both 16- and 32-bit
code. Can we make crudasm (and maybe ndisasm) "switch gears" in the
middle of a disassembly?

Nathan.
From: Wolfgang Kern on

Frank Kotler mentioned:
....
> ... So many bits, so little amBITion!
:)
only those who care every single bit are granted the title 'master' :)
it's anyway a hard and encumbering way of programming, but the resulting
code gives a feeling of being superior over all what's around so far, and
there is much more power in ASM/machine code than HLL-coders may even be
able to imagine.
__
wolfgang



From: Wolfgang Kern on

Nathan wrote:
[have to quote it myself again]
>> Jeez, you're gettin' good at this, Nathan! You too, Willow! Sure enough,

> Well, better would be something like what is at the bottom of this
> page:

http://mrbook.org/tutorials/make/

> We will need to start it like this:

> CCPP=g++
> =gcc

>>ie: I unwrapped the fine work of my newsreader, it built without
>> complaint, and disassembles files!

>>> ...or maybe someone here will script you a
>>> better one if they aren't too busy testing the latest "Stdlib duo"
>>> powered .net assembler.

>> "Stdlib duo" :) :) :) I like it!

>> If/when I get out of the "lazy hole" I've been in lately (worse than
>> usual!), I'll try "crudasm1" on something more "challenging", but it

> I think that Wolfgang's 'disass.com' might contain both 16- and 32-bit
> code. Can we make crudasm (and maybe ndisasm) "switch gears" in the
> middle of a disassembly?

Why not ?
a disassembler could be able to detect code flow and mode changes within
the code under test also in a static analysis and insert 'use16/use32'.
And that's just one point why I designed my 'DisAss core' this way.
__
wolfgang