Oto błąd w Matriksie, który wygenerował(a) agent(ka) jeff:
>Groan... ignore my previous email about recompiling the library.
>The AsmPlan program does not use the library.  I now think the
>problem can be found in a file called "subs.inc".  Look for a line
>like this:
>   db  "\"      ;\
>nasm added a feature that uses the "\" as a comment continuation
>just like in "c" programs.  I'm not sure what version it appeared in
>but the feature is not in version 98.22.
You are right it is line 547 in subs.inc
   db "\",0          ;65 \
after recompiling AsmPlan keys works but now I'll look for other bugs :]
--
QUASAR  http://www.quasar.prv.pl quasar2[at]o2.pl gg:3336919
	        jid:quasar[at]jabber.atman.pl

On 08/23/2005 03:50 pm, Frank Kotler wrote:

> I haven't looked at the new AsmPlan, but AsmEdit looks a lot better than
> a couple of versions ago. *Fantastic* documentation in the help files!
>
HI Frank,
Don't bother looking at AsmPlan.  I found a long list of problems
while looking for the infamous "\" bug.  It is amazing.  I use AsmPlan
every day but did not see these problems.  think I'll take a break
from the source-code-generator and work on AsmPlan for awhile.

It will be nice to work on a simple project.  The source-generator
got complex when it encountered the ELF format and dynamic
libraries.  Well, maybe not complex, more like tedious.  I've got
most of the work done but it needs some rework and AsmPlan
is more interesting.

  all the best, jeff

jeff wrote:
> the
> problem can be found in a file called "subs.inc".  Look for a line
> like this:
>    db  "\"      ;\
> nasm added a feature that uses the "\" as a comment continuation
> just like in "c" programs.  I'm not sure what version it appeared in
> but the feature is not in version 98.22.

I thought it sounded like it might be that one again. I recently got bit
by it myself in some code - and I *know* it's there. It *is* quite a
useful feature, but it *does* break existing code, occasionally.

> The easy fix is to remove the "\" at end of line or wait a few months
> for the next release.  This bug has bitten me numerous times now and
> is difficult to find.

Putting *anything* after the '\' will fix it. I usually go with:

      ...
      db 5Bh ; [
      db 5Ch ; / <- goddam Nasm line-continuation
      db 5Dh ; ]
      ...

It's a PITA, I agree, but it *is* deliberate.

I haven't looked at the new AsmPlan, but AsmEdit looks a lot better than
a couple of versions ago. *Fantastic* documentation in the help files!

Keep up the good work, Jeff!

Best,
Frank

Oto błąd w Matriksie, który wygenerował(a) agent(ka) jeff:
>
>I've also encountered this problem and fixed it by recompiling the
>library and reinstalling it.  Try going into the library directory and
>doing a  "make" then a "make install" as root.  Then recompile
>AsmPlan.
>
I've recompiled all by going to ~/asmide and typing
make clean
make
make install
but asmplan still doesn't work as expected.
>
>Right, the console does not support a mouse and AsmPlan
>requires a mouse.  I thought about adding a mouse driver for
>the console, but keep hoping someday the kernel will include
>a mouse driver.   For awhile there was a version of AsmPlan
>using GPM (general purpose mouse driver) but that conflicted
>with the goal of using only assembler libraries and code.
>
GPM is very common on all Linux ditributions and you may add it as
an option if you want to follow the way of using only assembler libraries.
User wants GPM - user use GPM.
--
QUASAR  http://www.quasar.prv.pl quasar2[at]o2.pl gg:3336919
	        jid:quasar[at]jabber.atman.pl

On 08/22/2005 09:35 am, QUASAR wrote:
> Hi all!
> There is a problem with asmplan. When I run 'make install' then it works
> fine but when I compile my own version with nasm 0.98.37 or 0.98.39 then
> resulting binary doesn't properly recognize pressed keys for example:i

Groan... ignore my previous email about recompiling the library.
The AsmPlan program does not use the library.  I now think the
problem can be found in a file called "subs.inc".  Look for a line
like this:
    db  "\"      ;\
nasm added a feature that uses the "\" as a comment continuation
just like in "c" programs.  I'm not sure what version it appeared in
but the feature is not in version 98.22.

The easy fix is to remove the "\" at end of line or wait a few months
for the next release.  This bug has bitten me numerous times now and
is difficult to find.

If that does not fix the problem, let me know and I'll keep looking.

  all the best, jeff

On 08/22/2005 09:35 am, QUASAR wrote:
> Hi all!
> There is a problem with asmplan. When I run 'make install' then it works
> fine but when I compile my own version with nasm 0.98.37 or 0.98.39 then
> resulting binary doesn't properly recognize pressed keys for example:
> - when I press 'n' nothing happens.
> - when I press 's' it wants to add todo to list (like after 'a')
> - when I press 'd' it wants to find text
> and so on.i

I've also encountered this problem and fixed it by recompiling the
library and reinstalling it.  Try going into the library directory and
doing a  "make" then a "make install" as root.  Then recompile
AsmPlan.

The problem seems to be getting all the library module dependencies
between other library modules linked.  I thought it was fixed on the
latest version.. I'll check it.

> Also mouse doesn't work on console (but does under xterm).

Right, the console does not support a mouse and AsmPlan
requires a mouse.  I thought about adding a mouse driver for
the console, but keep hoping someday the kernel will include
a mouse driver.   For awhile there was a version of AsmPlan
using GPM (general purpose mouse driver) but that conflicted
with the goal of using only assembler libraries and code.

The AsmPlan program is scheduled for upgrading someday.
It also has a bug in the date handler which gives the wrong
data occasionally.  The problem doesn't keep me from
using the program, so we muddle on <grin>.  I've written
new data functions in the library that fix the problem
but need to integrate them into AsmPlan.  So many
projects, so little time..


  all the best, jeff

Hi all!
There is a problem with asmplan. When I run 'make install' then it works fine
but when I compile my own version with nasm 0.98.37 or 0.98.39 then resulting
binary doesn't properly recognize pressed keys for example:
- when I press 'n' nothing happens.
- when I press 's' it wants to add todo to list (like after 'a')
- when I press 'd' it wants to find text
and so on.
Also mouse doesn't work on console (but does under xterm).

--
QUASAR  http://www.quasar.prv.pl quasar2[at]o2.pl gg:3336919
	        jid:quasar[at]jabber.atman.pl

The following packages have been updated:

  AsmEdit - assembly editor
  AsmREf - reference for x86 linux assembly
  AsmLib - library of 270 functions
  AsmMgr - file manager and IDE frontend
  AsmFunc - minor functions to test crt and keyboard
  AsmMenu - script menu program

All programs are written in x86 assembler and can
be found at:

  http://members.save-net.com/jko%40save-net.com/asm
  http://sourceforge.net/projects/asmref
  http://sourceforge.net/projects/asmedit
  http://sourceforge.net/projects/asmlib
  http://sourceforge.net/projects/asmmgr

This update includes about a 100 bug fixes
  and some enhancements.  The disassembler
  for generating source from executable files
  is still in progress and a few months away.

  The library is now adding some high level functions
   to handle hash tables and browse directories.

   jko at bsn1 dot com

Anyone interested in the menu program for scripts can
find it on the web page along with some examples.  The
AsmIDE programs now use it instead of the "dialog"
program.

   http://members.save-net.com/jko%40save-net.com/

Skip this if not interested in script menus.

Scripts don't do menu's very well and the existing
solutions (dialog program and others) are not easy
to use.  I'm thinking about writting a menu program
that would be so simple an example would be enought
for most programmers.

A script menu is needed for AsmIDE and the library
now has most of the code needed.  It may be faster
than studying the diaglog program again and again.

What if.. we simply used an editor to put text were
we wanted buttons and let a program build the buttons?
We would need some way to tell the script a button was
pressed and identify the button.

If the button text was the end of a script
file it will be ignored if the shell.  Well,
we would have to put a "exit" command in the
script to keep it from finding our button text,
but that's not a problem.

We could assume the buttons form a grid and identify
each button with coordinates.  With coordinates the
button locations and return codes are obvious just by
looking at a picture of the buttons (text).  Both the
script and button display program can find the grid
structure and don't need to pass any parameters to associate
a button with a specific code.

OK, the only problem left is to make sure the grid does
not contain irregular buttons or huge buttons that make
things confusing.  This can be solved by making all buttons
the same size.  Having everything the same size is a
limitation, but if we allow buttons to be optional in
a grid position it is still possible to make some interesting
menus.

So, can this be written easily and quickly in assembler?
Decoding a text button with multiple lines of text can be
difficult.  Then, there is the problem of adjusting button
positions and determining window size.

I'll give this project a go, and see what happens.

  all the best, jeff

Assembler programs released this week:

   http://members.save-net.com/jko%40save-net.com/asm/

AsmMgr program now has a project module with
these features:
  * tracks projects and opens project directories
  * builds makefiles, sample programs, and debug scripts.
  * handles most assemblers and tools.
  * displays installed tools (debuggers, assemblers, etc.)

AsmPub is a program to extract comments for source
file and build documents.

CrtTest is a simple program to test console and xterm
features.  This program is included in the AsmFunc
package of programs.

Most of the other AsmIDE programs have been updated
with bug fixes or documentation improvements as noted
below:
   AsmRef - updated documents
   AsmEdit - minor bug fixes
   AsmLib - Bug fixes, new functions
   Asmfunc - minor improvements, structure change
   AsmPlan - unchanged.

   http://members.save-net.com/jko%40save-net.com/asm/

It's Done...

The AsmMgr program now has a project module with
these features:

  * tracks projects and opens project directories
  * builds makefiles, sample programs, and debug scripts.
  * handles most assemblers and tools.
  * displays installed tools (debuggers, assemblers, etc.)

All this works for simple projects and will be useful
to new programmers.  The assemblers supported
are: gas, nasm, yasm, and fasm

Also, the AsmMgr had another batch of bugs fixed.  Mostly,
the terminal handling was imporved.

Have not updated Sourceforge yet, but the latest is on:

   http://members.save-net.com/jko%40save-net.com/asm/

What next?  Anyone have ideas about what is needed?
My list of possible projects include: a document builder,
a debugger, a scrip menu, or a rewrite of AsmPlan.

  all the best, jeff

Another update to AsmIDE is on the web site at:

  http://members.save-net.com/jko%40save-net.com/asm/

Changes include: lots of bug fixes in AsmMgr
                  new program to test crt state
                  minor changes to AsmRef (more soon)
                  buf fixes in AsmEdit and AsmLib

It has taken awhile to get the library function "sys_wrap"
working.  It now works and allows AsmMgr to control
other programs by feeding keystrokes and capturing output.
This will probaby be used by the debugger project whenever
it starts.

In other news, sourceforge now has the AsmRef project
hosted.

   http://sourceforge.net/projects/asmref

I'm thinking about delaying the debugger project for awhile
and doing more work on AsmMgr.  It has now  replaced mc on
my desktop.  With a little more work it can become a powerful
file manager.  A very small package (about 1/10 the size of
other managers).

  all the best, jeff

It is amazing how many bugs can hide in
a program.  My testing must have always typed
commands in the same way and bugs did not appear.
Anyway, The AsmIDE programs are getting closer
to release and new versions are on the web site.
Thanks to those who reported problems.

I did not bother to update the change logs
due to the large number of changes.

   AsmRef - extensive menu driven help system.
            This is a much improved version with
            about 30 files of interest to assembly
            programmers.
            (menu selection problems fixed)

   AsmMgr - a "mc" style file manager which has been
            configured for smIDE.  It will do normal
            file minipulation and kick off compilers,
            etc.
            (Lots of bug fixes and improvements, a few
             more changes are planned)

   AsmLib - Library of about 160 functions for Linux
            x86 programming (console or terminal).
            (the library had 3 bugs and is now approaching
             170 functions)

   AsmEdit - A general purpose editor with hooks for
            assembly programmers.  This version has a
            few bug fixes, and some reorginization.

   AsmFunc - General functions to enhance AsmEdit and
            AsmMgr.  Also, a few general programs that
            did not fit anywhere else.

   AsmPlan - This an alpha program that will be redesigned
            soon.  It is mostly a place holder for now,
            but it does provide a somewhat useful todo
            program.

All of these programs are on the web page at:
   http://members.save-net.com/jko%40save-net.com/asm/

Any feedback is appreciated.  If no bugs pop out this
release will get distributed within a few days.

  all the best, jeff

Hello all,

An incremental release of AsmIDE programs may
occur this week.  The package was broken
into smaller releases to solve some problems
and make updating easier.  It now consists of
the following:

   AsmRef - extensive menu driven help system.
            This is a much improved version with
            about 30 files of interest to assembly
            programmers.

   AsmMgr - a "mc" style file manager which has been
            configured for smIDE.  It will do normal
            file minipulation and kick off compilers,
            etc.

   AsmLib - Library of about 160 functions for Linux
            x86 programming (console or terminal).

   AsmEdit - A general purpose editor with hooks for
            assembly programmers.  This version has a
            few bug fixes, and some reorginization.

   AsmFunc - General functions to enhance AsmEdit and
            AsmMgr.  Also, a few general programs that
            did not fit anywhere else.

   AsmPlan - This an alpha program that will be redesigned
            soon.  It is mostly a place holder for now,
            but it does provide a somewhat useful todo
            program.

All of these programs are on the web page at:
   http://members.save-net.com/jko%40save-net.com/asm/

This notice will be sent to a few other lists, so
any feedback on problems would be appreciated before
the packages get general distribution.  Assuming..
they do get distributed <grin>.  My interest at present
is to dive into the debugger and forget about polishing
the current release.

  all the best, jeff

The AsmEdit files have been updated on
Sourceforge:

  http://sourceforge.net/projects/asmedit

AsmEdit is an IDE for x86 assembler projects.
The major features are: library of assembler
functions, editor optimized for assembler,
help system for assembler coding, and a collection
of support programs.  Everything is written in
assembler.

This release includes an updated library and many
bug fixes in other areas.  The partially completed
front end is also present in demo form.  Comments
are encouraged.  The AsmEdit front-end is progressing
slowly and will not be available for a few months.
At this point the library, editor, and help system
are functional.  Much work remains to be done on the
help system but it now has some data not easily
found elsewhere.

  jeff owens

Nasm 0.98.39 is available - but not on SourceForge quite
yet... they're having some "transitional difficulties" at
the moment. We'll get copies up there as soon as the release
system seems stable - couple days, probably.

Meanwhile:

http://www.kernel.org/pub/software/devel/nasm/

The "binaries" are not complete, but win32, djgpp, and Linux
are available, plus, of course, a source package. 0.98.39
goes from C89 to C99, which apparently is causing some build
problems with some compilers. If you need/want to build Nasm
from source, and you can't figure it out, holler for help.
If you *can* figure it out, *post* some help, please.

For djgpp, you need the "beta 2.04" version, for example
(Thanks to Bart Oldeman for that tip). The Makefile created
by "configure" in Linux (and rdoff/Makefile) needs "std=c99"
removed. (Mkfiles/Makefile.unx seems okay) I hope we'll have
a "cleanup release" out sooner than the year and a half that
this release took, but no promises.

I *really* hope that everyone will upgrade to 0.98.39 as
soon as possible! Why? Well... a "Serious Problem" has been
uncovered in Nasm - all versions prior to 0.98.39 (maybe not
*really* early versions). We all know enough  not to run
code from untrusted sources (I hope!). Turns out you're
vulnerable even *assembling* malicious source with Nasm.
Yes, a <line-noise> buffer overflow (potentially
exploitable). Betov gets "I told you so" rights. Not
actually *caused* by using C, but C provided the hole for us
to fall into. I am deeply embarrassed that this remained
undiscovered so long!

The vulnerability was discovered by Jonathan Rockaway (a
student - since Nasm was written by a student, this is
perhaps appropriate), reported to us by D.J.Bernstein (his
instructor). Fixed by Ed Beroset. Thanks to all involved!

Other than that, the changes aren't too exciting. Nice new
rdoff stuff from Yuri Zaporogets, for the few who use rdoff.
Otherwise minor cleanups not worth mentioning...

Please upgrade and get rid of that buffer overflow! If you
can't/won't upgrade, please *examine* any source code from
less-than-fully-trusted sources for anything that looks
"weird". AFAIK, no one is targetting Nasm, but... we don't
need this crap!

Best,
Frank

Frank Kotler <fbkotler@...> wrote:

> Well, the actual segfault happens at line 5539 - there's an invalid
> pointer in "fbuf_cursor_ptr".

This problem was interesting.  I think it was caused by
the Nasm collecting data for the .bss section.  I had made
a bad assumption.

While looking for this bug, two other bugs came along and
bit me (this is reason for slow response).  Mandrake 10.1
has a bug with fonts that caused AsmEdit printing to fail.
Anyone using programs a2ps or enscript will find their fonts
different from Mandrake 10.0.

The second bug is that mulitiple copies of "a" can not be
executed at the same time.  This means the tutorial will
not run reliabiably.  The next release will fix this.

> AsmEdit could easily be used with another assembler - Fasm or Yasm or
> Gas or HLA. That's the advantage of doing it as a "shell IDE". LuxAsm
> proposes to be a "fully integrated IDE" - the editor, assembler, and
> debugger (and maybe more, eventually) running in the same address space,

Whoa.. that is one ambitious goal.  It could be the basis of the
ultimate tool.  It would allow assembler development to look like
an interpreted language.  For example, the user could type in an
instruction and have it compiled and executed immediatly.  This
would be ideal for newbies.  The code-complie-debug phases get
merged together and we could have test as you go.  This would be
somewhat like a spellchecker that works while you type.

> There are a number of "toolkits" - Mosaic, and GTK... a couple GTK+
> examples from Yeoh in the "files" section of the Yahoo linux-nasm-users
> group...

There is a linux-nasm group?  Gotta go checkthat out!  As for libraries,
I'm not comfortable with the big monsters (GTK, etc.).  The smaller
libraries like SVGAlib and FB(something) look easier to use, but
even those libraries can produce bloated code.

> Another option is to talk to your X server via socketcalls, using the
> "protocol" directly, and bypassing any libraries entirely. Christian
> Fowelin's libASM has some X code done this way (but intended to be used
> as a library). I haven't really attempted this approach...

It would be interesting to see how much code is required to do socket
calls and produce a hello-world program.

> Oh, yes! Didn't I mention that LuxAsm is intended to assemble itself?
> We're even considering not using Xlib (but probably will, at first,
> anyway). I *told* you we were ambitious! :)

I had trouble finding programs using Xlib.  Even "c" programmers
said it was too difficult and wrote wrappers.  You are indeed
ambitious <grin>.

> The only LuxAsm code existing is a partial assembler. I've done an
> "experiment" in X - just an expansion of Numit_or's demo (which is an
> adaptation of Mammon's demo in Gas, I think) that uses Xlib very
> minimally, sticking to "do it yourself" as much as possible. It's very
> rudimentary, and *very* rough. The only thing it'll do is display (no
> scrolling or editing) the first few lines of its source code (if it
> doesn't find it, it just silently fails). It isn't much, but when it
> *does* work, it's the fastest thing I've ever seen happen in X, so I'm
> encouraged that "asm for X" may be worthwhile. (this is a good thing,
> since I don't know C very well! :)
>
> http://home.comcast.net/~fbkotler/lxtest4.tar.bz2

Thanks, it is good to see examples.  A few examples are worth more
to me than a stack of manuals.

Well... back at it.  Christmas set my coding back a few days and
I'm anxious to jump back in.

  all the best, jeff

jeff wrote:

> > When I type "a", my screen turns blue, and it segfaults.

> Thanks, I'll look for the bug...

Well, the actual segfault happens at line 5539 - there's an invalid
pointer in "fbuf_cursor_ptr". It's put there by line 3596, transferred
from "hist_cursor_ptr". I haven't yet figured out how the bad value is
getting into "hist_cursor_ptr"... It *seems* to be initialized to a
reasonable value, but must be getting clobbered somewhere... (and it
*is* a "first time" thing - once a.ini is created, it doesn't happen)

> and you are right about AsmEdit not
> having a very good first impression.  Hopefully, the next release will
> be better.

Yeah, *all* software can be improved, and "early" software most of all.
I think I've actually run AsmEdit in the debugger more than "run" it.
Seems a little "tweaky", but quite cool. Got a lot of potential! I'm a
"command line guy" myself (strange that I'm "nominal chief maintainer"
of LuxAsm, considering I don't use IDEs, but... life is strange...), but
a lot of people have been asking for an IDE for Nasm under Linux.
Something like NaGoA or RadAsm...

AsmEdit could easily be used with another assembler - Fasm or Yasm or
Gas or HLA. That's the advantage of doing it as a "shell IDE". LuxAsm
proposes to be a "fully integrated IDE" - the editor, assembler, and
debugger (and maybe more, eventually) running in the same address space,
so that the editor's syntax-highlighting (which *I* consider distracting
:) should be "perfect" - we'll ask the assembler what "part of speech"
we're looking at... if it isn't highlighted as you expect, then it won't
be assembled as you expect! No need for "symbolic debugging info" in the
file, the debugger will have access to the assembler's symbol table.
Etc... But there are disadvantages to this approach, too! Lord knows if
it'll ever amount to anything. Mostly high-falutin' ideas, at the
moment.

> Wow! That sounds great.  Have you looked at Yasm?  The author says
> he is tring to create a replacement for Nasm.  Don't know much about
> it.

Yeah, Peter Johnson originally thought of Yasm as a sort of "Nasm 2.0",
but it's pretty much taken on a life of its own. I haven't looked at it
at all, lately, but I guess it's at a "useable" stage...

> I started out looking at Xlib in hopes of doing assembler tools in
> X but did not like it very much.

"I don't think we're in Kansas anymore, Toto!" :)

> Maybe other libraries would be better?

There are a number of "toolkits" - Mosaic, and GTK... a couple GTK+
examples from Yeoh in the "files" section of the Yahoo linux-nasm-users
group...

Another option is to talk to your X server via socketcalls, using the
"protocol" directly, and bypassing any libraries entirely. Christian
Fowelin's libASM has some X code done this way (but intended to be used
as a library). I haven't really attempted this approach...

> Doubt you will be doing any assembler code for X,

Oh, yes! Didn't I mention that LuxAsm is intended to assemble itself?
We're even considering not using Xlib (but probably will, at first,
anyway). I *told* you we were ambitious! :)

> but you are welcome
> to use anything from AsmEdit.

And likewise, of course - we're all GPL, here. I've been thinking we'll
want to look at the e3 code... but X is *so* different, there may not be
too much we can use back and forth...

> At this point it is pretty rought but
> mostly functional.

The only LuxAsm code existing is a partial assembler. I've done an
"experiment" in X - just an expansion of Numit_or's demo (which is an
adaptation of Mammon's demo in Gas, I think) that uses Xlib very
minimally, sticking to "do it yourself" as much as possible. It's very
rudimentary, and *very* rough. The only thing it'll do is display (no
scrolling or editing) the first few lines of its source code (if it
doesn't find it, it just silently fails). It isn't much, but when it
*does* work, it's the fastest thing I've ever seen happen in X, so I'm
encouraged that "asm for X" may be worthwhile. (this is a good thing,
since I don't know C very well! :)

http://home.comcast.net/~fbkotler/lxtest4.tar.bz2

(although the executable is called luxasm, this is *not* LuxAsm!) If
you're interested in "asm for X", there are so few examples that even
this poor one might be worth looking at...

Best,
Frank

On Wed, 22 Dec 2004 15:30:00 +0530
sandeep <sandeep@...> wrote:

> IMHO it would be good to keep the documentation in tune with the existing
state
> of affairs. Once basic documentation is in place, keeping it with code may not
> be as much work, as writing fresh at later stage, by that time somethings may
be
> forgotten.

Yes, I think you are correct about doing documentation as the
code progresses.  I've started using Robodoc to extract comments
out of the code but it isn't working very well.  I've considered
writing a documentation program just for assembler.  Maybe that is
the best answer?

> more than ten years back, i had also implemented a simple editor in assembly
on
> dos as a part of course project.

Ah... DOS.  I miss all the tools available for DOS.
This Linux assembly programming is like reinventing the wheel.
Well.. that isn't completly true, some tools are better, but
mosty assembly is ignored by the Unix world.

On Wed, 22 Dec 2004 08:52:14 -0500
Frank Kotler <fbkotler@...> wrote:

> When I type "a", my screen turns blue, and it segfaults. With a
> parameter provided, it works, but this creates a terrible first
> impression! I haven't looked into it enough to spot the problem. Since I
> think it's a "first time only" problem, I thought I'd mention it, in
> case you don't see it anymore.

Thanks, I'll look for the bug... and you are right about AsmEdit not
having a very good first impression.  Hopefully, the next release will
be better.

> I'm involved in a similar project - LuxAsm - somewhat more ambitious -
> for X, and with an "integrated" assembler. (maybe *too* ambitious... we
> shall see). Also at SourceForge. Check us out, if you get a chance. No
> code to report bugs on yet :) We're still in the "planning" stages.

Wow! That sounds great.  Have you looked at Yasm?  The author says
he is tring to create a replacement for Nasm.  Don't know much about
it.

I started out looking at Xlib in hopes of doing assembler tools in
X but did not like it very much.  Maybe other libraries would be better?
Doubt you will be doing any assembler code for X, but you are welcome
to use anything from AsmEdit.  At this point it is pretty rought but
mostly functional.

  all the best, jeff

jeff wrote:
>
> AsmEdit status report
> December 19, 2004
>
> The library (AsmLib) has grown to about 140 functions.
> It now handles times, dates, plus many minor additions.
>
> The IDE front end design has been completed and looks
> somewhat like the "mc" file manager.  The program shell
> now runs and a few buttons are working.

Hi Jeff,

When I type "a", my screen turns blue, and it segfaults. With a
parameter provided, it works, but this creates a terrible first
impression! I haven't looked into it enough to spot the problem. Since I
think it's a "first time only" problem, I thought I'd mention it, in
case you don't see it anymore.

I'm involved in a similar project - LuxAsm - somewhat more ambitious -
for X, and with an "integrated" assembler. (maybe *too* ambitious... we
shall see). Also at SourceForge. Check us out, if you get a chance. No
code to report bugs on yet :) We're still in the "planning" stages.

Best,
Frank

jeff wrote:
> Documentation improvements were also suggested but ended up
> at the bottem of a wish list.  Once the code is stable there
> will be more time to work on documentation.
IMHO it would be good to keep the documentation in tune with the existing state
of affairs. Once basic documentation is in place, keeping it with code may not
be as much work, as writing fresh at later stage, by that time somethings may be
forgotten. and documentation is most boring thing in a project if you ask any
programmer. adding/subtracting is easier. as my experience tells.
documentation can also be part of cvs.

i know it may be difficult, as assembly work is quite fun and needs attention.
more than ten years back, i had also implemented a simple editor in assembly on
dos as a part of course project.

--
regards
sandeep
--------------------------------------------------------------------------
visit me at http://members.fortunecity.com/sandeepkumar/

When a fly lands on the ceiling, does it do a half roll or a half
loop?
--------------------------------------------------------------------------

AsmEdit status report
December 19, 2004

The library (AsmLib) has grown to about 140 functions.
It now handles times, dates, plus many minor additions.

The IDE front end design has been completed and looks
somewhat like the "mc" file manager.  The program shell
now runs and a few buttons are working.

The goal is to automate everything for someone
new to assembler.  The system will be checked to verify an
assembler has been installed and new projects will be setup
with template files for source and "make".

Handling of debuggers is still being studied.  To make setup
easier an integrated debugger would be nice, but may be
too much work.

If anyone wants to suggest a feature or special need, now is
a good time.  One person did suggest the editor needs to be
a selection in  the IDE and that has been implemented.
Documentation improvements were also suggested but ended up
at the bottem of a wish list.  Once the code is stable there
will be more time to work on documentation.

  all the best, jeff

AsmEdit responses,

Actually, there were no responses from this
list but others have looked at AsmEdit and
responded with:

  1. Interface is too confusing.
  2. Too much setup.
  3. Documentation isn't organized well.

It looks like a wrapper is needed to set
everything up and initiate projects.  I've
started a design with these goals:

  1. check installed tools and warn if
     any are missing.
  2. provide a directory with project template
     including the initial source file and
     a working makefile.  This will be created
     by a "new project" button.
  3. write a front end program that also serves
     as a file manager.
  4. keep list of projects and provide
     selection window.

All this will reduce setup and hide the basic
engine.  All the user will see initially is
a row of project buttons to add, delete, or
work with projects.  Below the project buttons
will be a simple file manager to organize files
among directories.

Any other suggestions?

jeff

Whoops, ignore the web address in previous
announcement.  Hopefully, this one will work
better..

Hello all,

The next update to AsmEdit is completed and a
small web page created for it.  This  version
is a major upgrade with the following features:

  * library of assembler functions build in.
  * Extensive help and reference section for
    library, kernel calls, x86 assembly, and
    more.
  * simple planer and note taker build in.
  * configuration and install program added
  * user interface improved
  * numerous bugs removed and minor improvements
    in most areas.

In a few days it will be announced on other
lists, but any comments would be much appreciated.
Mosly, I need to know if the web page is confusing
or if the program works on other systems.

the web page is:

http://members.save-net.com/jko%40save-net.com/asm

There is much todo yet but hopefully this release
will create more interest.  It is in constant use
here and a great time saver.

  jeff

ps.. this message created by AsmEdit

Hello all,

The next update to AsmEdit is completed and a
small web page created for it.  This  version
is a major upgrade with the following features:

  * library of assembler functions build in.
  * Extensive help and reference section for
    library, kernel calls, x86 assembly, and
    more.
  * simple planer and note taker build in.
  * configuration and install program added
  * user interface improved
  * numerous bugs removed and minor improvements
    in most areas.

In a few days it will be announced on other
lists, but any comments would be much appreciated.
Mosly, I need to know if the web page is confusing
or if the program works on other systems.

the web page is:

http://www.members.save-net.com/jko%40save-net.com

There is much todo yet but hopefully this release
will create more interest.  It is in constant use
here and a great time saver.

  jeff

ps.. this message created by AsmEdit

Hello, DesktopLinuxAsm

It appears very few people are interested in Linux
assembly for the desktop.  There are less than 4
of us.  No problem, I'm enjoying all this and will
continue.

The web page has been updated with a few improvements
and data from my research into signals.  The snippet
file signal.asm has been added.  It is a stand alone
program and also acts as a tutorial.  Comments in the
program are taken from man pages and other documents.

For some reason it took me a long time to feel comfortable
with signals.  The passing of parameters seemed obscure
and all those symbolic names were difficult to track
down.  With signal.asm the topic should now be much
easier to understand and hopefully a programmers can
look at the source and have signals going in a few
minutes.

  all the best, jeff
  DesktopLinuxAsm@yahoogroups.com
  http://members.bsn1.net/jko@save-net.com/asm/

The AsmEdit program has been updated to fix
bugs.  A new version is now on SourceForge at:
http://sourceforge.net/projects/asmedit

AsmEdit is an editor which can also function
as an IDE for assembler developement.  It isn't
for everyone.  Probably, only programmers who
have worked with Alter or Mbedit will want to
use it... Then again, many programmers like the
mode style editors based on 'vi' so AsmEdit may
be of general interest.

AsmEdit is a mode style editor with the following
features:

  * external helper programs for spelling, compiling,
    debugging, printing, etc.
  * paragraphing
  * simple calculator
  * hex input and display
  * mouse integration
  * works with either mouse buttons or keyboard
  * hidden menu's triggered by mouse actions
  * source highlighting for .asm files.

New Site for Desktop Assembly
http://members/bsn1.net/jko@save-net.com/asm/

The DesktopLinuxAssembly site is being created and
presently has two projects, some code snippets
and information about desktop programming.

One project is registered at Sourceforge
http://sourceforge.net/projects/asmedit

Work on a library is scheduled for the future
along with code filter to transport source between
nasm and gas formats.  Participation or comments
are welcome.