nasm-users — Discussion and help for Nasm users.

Re: [Nasm-users] Why is my nasm program killing itself?

[Frank K. <fbk...@ve...>]

ivanatora wrote:
> Frank, I've tried that source on several machines and it gets killed
> on both of them. These include kernel versions:
> 2.6.23.9
> 2.6.21.5
> 2.6.12.4

Oh, oh!

> I've tried your code and it runs perfect. I even replaced mov eax, 1
> with mov al,1 and it still works. I removed nops and it works. Removed
> even the .data section and it works.
> I've moved back to my code and tried something else. I removed
> the .bss section and the program didn't get killed!
> So mov al,1 is working at all :)
> I replaced the .bss section with:
> section .data
>         x db 0x1
> and the program is not getting killed.

Stranger and stranger! Your original code had a variable in .bss, and 
you could write to it once, but not twice, right? So it isn't an 
"absolute prohibition" on .bss. In that case, the size of .bss didn't 
change, but its position did, and alignment(?). Default alignment for 
.bss is 4 - might try "section .bss align=16" or 64, or even 4096. I 
like "trial and error", but this is ridiculous! The answer's in the 
source, somewhere...

I've advised the "nasm-users" list at SF about this. I'll cc this to 
'em, just to update 'em on the kernel versions. I was hoping this was a 
"one time" deal, but I guess not...

I'm completely baffled!

> Now I'm loading AL or AX or EAX, even doing division :)
> Btw, how can I see the contents of a variable in gdb? I can see
> registers with "info registers", but I want to see what x is look like.

(assemble with the "-g" switch!)

"print x", apparently. (printf, too, apparently, but it's complaining 
about my format string having a missing '"'!) You might be interseted in 
this:

http://www.ffnn.nl/pages/articles/linux/gdb-gnu-debugger-intro.php

And/or:

http://linuxfocus.berlios.de/English/July2004/article343.shtml

(thanks again, Nathan!)

Besides "man gdb" and "info gdb", a google for "gdb tutorial" finds a 
flock of 'em. If you *really* want to get into gdb:

http://www.ffnn.nl/pages/articles/linux/gdb-gnu-debugger-intro.php

But I don't think gdb is going to help with this problem(?).

Best,
Frank

Re: [Nasm-users] Talk, don't spam

[Frank K. <fbk...@ve...>]

H. Peter Anvin wrote:
> Frank Kotler wrote:
> 
>>I also found a way to subject this list to "emergency moderation", which 
>>I have done. I don't know if that'll help - this is kind of a "test 
>>message" to see what it does...
> 
> The easiest is to set the list to "subscriber post only".  This means 
> that only registered list members can post, which filters out virtually 
> all spammers.

That's the option I was looking for. I'll look again. What I've done 
seems to be asking me for approval after the fact...

On a completely different topic, but still "talk", I'm wondering if you, 
or someone, can help me. There's an issue come up on alt.lang.asm (yeah, 
I know...) under the subject "Why is my nasm program killing itself". A 
guy has got Slackware 12.0 - kernel 2.6.21.5, apparently, and is having 
apparently good programs being "killed". Looks like they're killing the 
loader, actually... His disassembly suggests it's not a Nasm or ld 
problem...

We saw something in kernels 2.6.10 - 2.6.16 (approximately) where 
programs without a writeable section last were causing a SIGSEGV in the 
loader (fs/binfmt_elf.c, IIRC) - original patch threw SIGKILL. I suspect 
something similar here.

I "should" learn my way around the kernel well enough to be able to find 
something like this myself, but I'm hoping someone more familiar can 
bail me out and suggest some workaround for this guy - an "align" 
directive or ???? - that'll make his programs work without having to 
reinstall. He's getting the impression that asm is difficult!

TIA for any help or suggestions!

Best,
Frank

Re: [Nasm-users] Talk, don't spam

[H. P. A. <hp...@zy...>]

Frank Kotler wrote:
> 
> I also found a way to subject this list to "emergency moderation", which 
> I have done. I don't know if that'll help - this is kind of a "test 
> message" to see what it does...
> 

The easiest is to set the list to "subscriber post only".  This means 
that only registered list members can post, which filters out virtually 
all spammers.

For people whose post address is different from their subscription 
address (like it often is for me), Mailman has this lovely feature of 
being able to subscribe to a list but set it to "no mail", so you have 
your post address registered as a valid member, but it doesn't get the mail.

	-hpa

[Nasm-users] Talk, don't spam

[Frank K. <fbk...@ve...>]

Hi List,

As you may have noticed, the spammers have found this list! :(

As "owner", it is my responsibility to do something about this. Poking 
around the delightful SF/mailman interface, I'm not having a lot of 
luck. Found the way to "exclude" messages from the public archive, but 
it's tedious as hell and they don't really go away. I did a few messages 
and got sick of it... I may get back to it...

I also found a way to subject this list to "emergency moderation", which 
I have done. I don't know if that'll help - this is kind of a "test 
message" to see what it does...

Since this list isn't used much, I considered "killing" it entirely... 
but apparently I can't do that. "Once open source, always open source" I 
suppose spammers got "freedom" too... sigh...

An alternative would be to drown the bastards out with chatter about 
Nasm... not much hope of *that*! :)

Hopefully, I can find some way to deal with it. If anyone has code for a 
virus that'll make a spammer's keyboard melt into their lap, that might 
help. (just joking - please *don't* post any malware!)

My apologies for the rude noises.

Best,
Frank

[Nasm-users] Male tool upgrading

[Clyde R. <Cl...@ii...>]

Do you think you can't improve what nature gave you? We will make you change your mind!
Once you have taken this remedy for some time, you'll start seeing the results!
http://Difieted.com/

[Nasm-users] Change your life today

[ade C. <pan...@WA...>]

Sharon gasped in pleasure when she saw my new large joystick in my pants


http://www.Waevelly.com/
3 inches or your money back

[Nasm-users] Latino hunks in gay sex scandal

[Hung s. <hel...@NI...>]

Don't be second best, hang huge and large

[Nasm-users] Look at those jugs

[Nataly E. <hgi...@NI...>]

Women love men with a huge tool in their pants

Re: [Nasm-users] [nasm-devel] new learner

[Frank K. <fbk...@ve...>]

tihaashik wrote:
> 
> 
> Hello,I am new in assembly language and it seems quite difficult for
> me.but as it is one of the subject I need to learn as a part of
> syylebus in undergraduation courses I am at wits end about what to do
> can anyone tell me step by step how to learn assembly language?

Isn't that why you're taking the courses? :)

Well... First, this mailing-list is for the use of Nasm developers 
discussing the development of Nasm. Second, it's obsolete - kept around 
only for "archival" purposes. Current Nasm development is at 
http://nasm.sf.net and the list(s) you'll find there. The "nasm-users" 
list there was specifically created to keep this kind of question off 
the "nasm-devel" list... it isn't very active. :(

So... "step by step"... sounds perfect for Jeff Duntemann's "Assembly 
Language Step By Step"! :)

http://www.duntemann.com/assembly.htm

Another good beginner's resource, this one for 32-bit asm:

http://www.drpaulcarter.com/pcasm/

Jonathan Bartlett's "Programming From The Ground Up" is another nice 
book that starts from the beginning, but uses (G)as syntax (AT&T) rather 
than Nasm.

http://www.cafepress.com/bartlettpublish.8640017

Or the "free, as in freeloader" version:

http://savannah.nongnu.org/projects/pgubook/

The examples from that book have been translated to Nasm syntax, and are 
available here:

http://mysite.verizon.net/fbkotler/nasm-pgu-examples.tar.bz2

if you'd care to attempt to read the book about Gas and use Nasm...

These are all "step by step", "from the beginning" approaches. In the 
context of a cs curriculum, you presumably know some high level 
language(s) before encountering assembly language. There's an apporoach 
which proposes to "leverage" that knowledge and ease you into asm "from 
the top, down" - Randy Hyde's "Art of Assembly Language Programming":

http://webster.cs.ucr.edu/AoA/index.html

This uses HLA... which uses a very different syntax from Nasm. I 
personally much prefer the "bottom up" approach, but this *is* intended 
for your presumed situation... (and poke around that site! there are 
links to *all* kinds of asm resources!)

But wait... if you're in a cs course, "Assembly Language and Machine 
Architecture" or some such is in your future (sounds like you're not 
taking it now? or taking it but not getting it?) How are *they* doing 
it? If they're teaching MIX or some such, learning Nasm-for-x86 may not 
help you much. Well it will, probably, but not directly ("perspective" 
is nice... as long as it doesn't lead to "confusion"). If they're still 
teaching Tasm-for-dos... you could follow along using Nasm. If they're 
using HLA, you're stuck with it. Wash your hands after. :)

There are lists here at !Yahoo! for win32-nasm-users and 
linux-nasm-users and Jeff Owens' DesktopLinuxAsm - depending on what you 
want to do. I'll cc this to the nasm-users list at SourceForge (we need 
the business). There's the "Beginner's Questions" forum at SF, too. If 
you can cope with usenet, news:alt.lang.asm and news:comp.lang.asm.x86 
are good places to ask questions... if by any chance you have any... :)

I guess the first thing for you to do is determine what OS you'll be 
programming for, and get "hello world" to assemble and run. Then, or 
before, you'll probably have more specific questions. Talk to ya later.

Best,
Frank

[Nasm-users] onticola

[onrot <onr...@Ma...>]

http://www.foolagsines.com/
Make your lady love you even more with your new, massive rod.

[Nasm-users] shukioku

[<shi...@es...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Can she handle it if you add 3 inches where it matters most? She'd<br>
LOVE it <a href="http://kdiaeita.com/">http://kdiaeita.com/</a><br>
</html>

[Nasm-users] kobe

[Stephanie M. <Ste...@LY...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Once a day for one more inch a month <a href="http://dopoiess.com/">http://dopoiess.com/</a><br>
</html>

[Nasm-users] leonoren

[ersun M. <ers...@co...>]

Big Dicks, Big Egos, No Risk!  VPXL Herbal! http://bluntaur.com/

[Nasm-users] amaabm

[DaeHee B. <Ber...@on...>]

Enhance your sex life, the easy way today http://lastjsdgf.com/

[Nasm-users] vorgeseh

[paris S. <par...@nw...>]

never be nervous in bed again with a big strong dick http://leceria.com/

[Nasm-users] jmerijen

[valami I. <Itk...@bo...>]

Rock-solid erections that feel bigger, wider and fuller =
http://www.ekonisia.com/

[Nasm-users] freiabon

[Kanyi k. <ko...@he...>]

over 1 million men around the world who are completely satisfied about the quality and effectiveness

Jouko Pullicino
http://wwwhyde.com/

[Nasm-users] An_v

[An_v <tng...@ya...>]

OnLine help on kasamba.com/An-v/
Assembler and other...
-- 
View this message in context: http://www.nabble.com/An_v-tf4663707.html#a13322530
Sent from the nasm-users mailing list archive at Nabble.com.

[Nasm-users] tfirhcsf

[mayan S. <Se...@hi...>]

hello lovely nasm-users
adding 3 inches to my cock sure has helped me out
http://www.figogoal.com/

mayan Sethi

Re: [Nasm-users] Can I use nasm in the sparc environment

[Frank K. <fbk...@ve...>]

nasm_user wrote:

...
> But the type of nasm-0.99.04.tar.bz2 is platform 
> independent according to the download web page.

The source code is platform independent - Nasm "should" compile and run 
on your Sparc - apparently it did... which I'm pleased to hear! However, 
Nasm outputs x86 code only.

>      How can I solve this problem?

I'm afraid you'll have to use a Sparc assembler. (G)as, probably - I 
really have no idea what's available. This assumes you want to run the 
resulting executable on the Sparc. If you want to develop on the Sparc, 
and run the resulting executable on x86, Nasm would work, but you'd need 
an appropriate linker (a "cross-linker"? Sounds horrible! :), or 
transfer the Nasm-produced .o file to a machine that has one.

>     I'm looking forward to hearing from you.

Well... sorry to have to tell you that Nasm won't produce code that'll 
run on Sparc. Thanks for the feedback - good to know that you got as far 
as getting an .o file out of Nasm on it!

Best,
Frank

Re: [Nasm-users] Can I use nasm in the sparc environment

[anonymous c. <nas...@us...>]

> The machine type in the ELF file is EM_386 which is
> for an x86 processor and is incompatible with sparc.

As expected. NASM knows how to assemble x86 code.
It does not know how to assemble Sparc code.

> But the type of nasm-0.99.04.tar.bz2 is platform
> independent according to the download web page.

Here "platform independent" means that NASM will run
on various platforms.

> How can I solve this problem?

Use an assembler that supports Sparc code.

[Nasm-users] Can I use nasm in the sparc environment

[nasm_user <nas...@16...>]

Dear experts:     I have a problem when I use nasm. It's like this:     1.I=
 installed the nasm program with the file of nasm-0.99.04.tar.bz2 ona remot=
e system which I log on whith the software of secureCRT. If I use the shell=
 command:     uname -a, the result is:  SunOS t1000 5.10 Generic_118833-33 =
sun4v sparc SUNW,Sun-Fire-T1000 Solaris  It means the CPU is not one of x86=
 series.     2. I wrote an assembly source file called test.asm, and I comp=
iled it using:     nasm -f elf test.asm     So the file test.o was generate=
d. Next I used the command: file test.o     the result is:     test.o:     =
    ELF 32-bit LSB relocatable 80386 Version 1     (I think here is where g=
oes wrong,because I see 80386 instead of sparc)     3. finally, I used :   =
  ld -o test test.o     then, error ocurred,and the result was:     ld: fat=
al: file test.o: wrong ELF machine type: EM_386     ld: fatal: File process=
ing errors. No output written to test         The machine type in the ELF f=
ile is EM_386 which is for an x86 processor and is incompatible with sparc.=
It should be EM_SPARC for the sparc processor.But the type of nasm-0.99.04.=
tar.bz2 is platform independent according to the download web page.
     How can I solve this problem?     I'm looking forward to hearing from =
you.                                                                 Best W=
ishes  

Re: [Nasm-users] New Re: problem with installation

[Frank K. <fbk...@ve...>]

Rod Pemberton wrote:
> Posted to GMANE's nntp version of  nas...@li... i.e.,
> gmane.comp.lang.nasm.general:
> 
> "Frank Kotler" <fbk...@ve...> wrote in message
> news:470...@ve......
> 
>>RG Nurrahmat wrote:
>>
>>>I am having problem with installing .bz2 file (NASM source) from
>>>ftp://ftp.kernel.org/pub/software/devel/nasm/source/nasm-0.98.39.tar.bz2
>>>, however, during installation with (MINGW32) MSys, I had this error
>>>configure: error: NASM requires ISO C99 (specifically, "snprintf")
>>>after I typed the following,
> 
> 
> Anyone know if there a way to disable the snprintf check during the NASM
> configure?  For example, DJGPP v2.03 uses GCC but doesn't use GLIBC.  v2.03
> uses a custom C library which doesn't have snprintf.  One could build
> w/DJGPP v2.04 which has snprintf(), but if one needed, wanted, or prefers
> v2.03, they'd implement their own snprintf() equivalent which won't pass the
> snprintf check, correct?
> 
> Personally, I'd prefer that NASM be ISO C90 or be able to fallback to ISO
> C90 if ISO C99 isn't available, for the reason you've mentioned:
> 
> 
>>>I was under the impression that "almost any" compiler would conform to
> 
> C99 by now, but it turns out "almost none" of 'em do.

It's a work in progress. HPA checked in some stuff overnight which I 
believe addresses this issue. The lastest 20071003 should have it.

ftp://ftp.zytor.com/pub/nasm/snapshots/

Folks who prefer to use obsolete tools - and I'm generally one of 'em - 
do so at their own risk. I'm sure Nasm isn't the only project that uses 
snprintf! I'm sorry so many people are having trouble with it since 
0.98.39, but we wanted to fix that buffer overflow, and snprintf seemed 
like the "modern" way to fix it. If available compilers don't have that 
capability, perhaps *that* should be considered a "problem".

Best,
Frank

Re: [Nasm-users] problem with installation

[H. P. A. <hp...@zy...>]

RG Nurrahmat wrote:
> Hi everyone,  
>  
> I am having problem with installing .bz2 file (NASM source) from 
> ftp://ftp.kernel.org/pub/software/devel/nasm/source/nasm-0.98.39.tar.bz2 
> , however, during installation with (MINGW32) MSys, I had this error  
> configure: error: NASM requires ISO C99 (specifically, "snprintf") 
> after I typed the following, 
> ./configure --prefix=/usr 
>  
> according to 
> http://arrozcru.no-ip.org/ffmpeg_wiki/tiki-index.php?page=NASM , these 
> are what I have to type 
> ./configure --prefix=/usr 
> make 
> mkdir -p /usr/man/man1 
> make install 
>  
> Thank you for your help.
> 

Get a newer mingw; my mingw from late January 2007 is fine.

	-hpa

Re: [Nasm-users] problem with installation

[Frank K. <fbk...@ve...>]

RG Nurrahmat wrote:
> Hi everyone,  
>  
> I am having problem with installing .bz2 file (NASM source) from 
> ftp://ftp.kernel.org/pub/software/devel/nasm/source/nasm-0.98.39.tar.bz2 
> , however, during installation with (MINGW32) MSys, I had this error  
> configure: error: NASM requires ISO C99 (specifically, "snprintf") 
> after I typed the following, 
> ./configure --prefix=/usr 
>  
> according to 
> http://arrozcru.no-ip.org/ffmpeg_wiki/tiki-index.php?page=NASM , these 
> are what I have to type 
> ./configure --prefix=/usr 
> make 
> mkdir -p /usr/man/man1 
> make install 
>  
> Thank you for your help.

Hi RG,

Yeah, Nasm requires C99 compliance - at least partial - for versions 
0.98.39 and up. The reason is that 0.98.38 and less had a potentially 
exploitable buffer overflow (more than one, I guess). Simply 
*assembling* some "malicious source code" could compromise your machine. 
(I don't think such "malicious source code" exists, besides the demo, 
but...) So reverting to 0.98.38 - which should "build anywhere" - is an 
option, but with risks.

I was under the impression that "almost any" compiler would conform to 
C99 by now, but it turns out "almost none" of 'em do. I thought Mingw 
gcc was fine... but this "bug report" suggests that C99 is a recent 
addition:

<http://www.mail-archive.com/deb...@li.../msg392485.html>

So I don't know what to make of that. If your gcc version is "old", 
updating it might help. (3.4.5 current?) Also, 0.99.04 is almost "ready 
for the world". That broke "build anywhere" even worse than 0.98.39, but 
workarounds for compilers that aren't happy with Nasm are being put in 
place. You *might* have better luck with the newer code - I wouldn't 
want to guarantee it. The "latest and greatest" - source *and* various 
executables... and docs - is available as a "nightly snapshot" at:

ftp://ftp.zytor.com/pub/nasm/snapshots/

You really *shouldn't* need the very latest compiler version to build 
Nasm, but I'm afraid perhaps you do... Probably worse with MS or Borland 
tools... Courage!

Best,
Frank