http://permalink.gmane.org/gmane.comp.lang.nasm.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.lang.nasm.general/324 <pre> Note: the "CPU" directive already exists, although it is limited in its support for recent machines. -hpa </pre> H. Peter Anvin 2011-12-02T02:08:18 http://permalink.gmane.org/gmane.comp.lang.nasm.general/323 <pre> Yes, it would be great to have. Looking forward to your patch. -hpa </pre> H. Peter Anvin 2011-11-21T18:36:14 http://permalink.gmane.org/gmane.comp.lang.nasm.general/322 <pre>I don't know, maybe others on the list do I don't know either, maybe others can respnd to that When assembling for Linux Elf, Nasm can generate STABS and DWARD debug information, which I think is what GDB wants. Yes, It is simple BSD, source is available from the main download page http://nasm.us/ ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 </pre> Jakob Bohm 2011-11-16T13:11:34 http://permalink.gmane.org/gmane.comp.lang.nasm.general/321 <pre>Hello. I'm starting a project that will be written in assembly language. I had intended to use HLA, but I can't get on their mailing list, and I'm hesitant to commit to using HLA without live support --- that is why I'm considering NASM now. What had impressed me about HLA was that it comes with a large library, and that programs can assemble for either Windows or Linux so long as the programs restrict themselves to using this library. Is there anything like that for NASM? Specifically, for console interface, file access and serial communication? It may be too complicated to support both Windows and Linux, in which case I will support Linux --- but it would be nice to support both. Also, other than the Windows/Linux issue, I was impressed with HLA's library in general. Are there any libraries of NASM code available? I would be interested in basic data-structure support (lists, arrays, associative arrays, etc.), such as I provided in my Forth novice package: http://www.forth.org/novice.html Is there a repo</pre> Hugh Aguilar 2011-11-03T06:12:19 http://permalink.gmane.org/gmane.comp.lang.nasm.general/320 <pre>Hi, I would like to suggest to add a –cpu option to the command line flags of nasm (somewhat similar to GCCs –march option) where the user can specify the CPU type he is programming for. If the user uses an instruction that is not supported by the CPU, the assembler can warn about this. This can help to keep code running on old machines. What do you think about this? Philipp------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1_______________________________________________ Nasm-users mailing list Nasm-users&lt; at &gt;lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nasm-users </pre> Philipp Kloke 2011-11-11T17:02:29 http://permalink.gmane.org/gmane.comp.lang.nasm.general/319 <pre> Hi Tyler, Just a WAG, but try _MessageBoxA&lt; at &gt;16 Not a whole lot of progress lately on Alink, AFAIK. There's an IDE and linker (based on Alink, I think) here: http://www.nasmide.co.nr/ This is a "work in progress", under active development (and looking for developers), so it may not be what you want, but I thought I'd mention it. If you try it (anyone), let us know what you think. Best, Frank ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-dev2dev </pre> Frank Kotler 2011-08-11T17:57:49 http://permalink.gmane.org/gmane.comp.lang.nasm.general/318 <pre>Hello all: I am writing a couple nasm functions to test this out with, and have been experiencing a problem. I want to link my nasm program to user32.lib, which I have done, but when I use the microsoft visual studio link command with user32.lib, I still get told that MessageBoxA is undefined. How do I do this? I am aware of alink, but it seems to be a work in progress and I'd rather just link to the normal libraries if I possibly can; help is appreciated. Thanks in advance, </pre> Littlefield, Tyler 2011-08-11T14:12:39 http://permalink.gmane.org/gmane.comp.lang.nasm.general/317 <pre> Hi Frank yes I can cancelled it - I worked out the answer myself. Ah, thanks - my solition was to use label_%[n] which also worked. I like %+n better though. Yep, the '*' was a typo ('*' is used as location counter in S390 assembler, iirc). I'm too lazy to use forums - I sometimes post a question, but then I forget where I posted it .... /Per ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev </pre> Per Jessen 2011-06-19T14:35:54 http://permalink.gmane.org/gmane.comp.lang.nasm.general/316 <pre>Hi Per, Hi List, As "owner" of this list, I got the following... blah, blah, blah... But when I logged in to approve it, I was informed that there were "no pending requests". Did you "cancel" it somehow, Per? (how?) Or is SF just messin' with me (us)? Well, I'll attempt to "answer" it anyhow! :) It's a better question than it might seem at first! At one time, in some cases, Nasm would have done what you want. But it's been "tightened up" in recent versions, and you really need to use the "%+" operator! label_%+n: This generates "label_1:", "label_2:", etc. Nasm complains about "somecode" being redefined... so I replaced that with... well... "some code"... just "ret" to begin with. Same code in each "label" doesn't seem useful, but it worked... as long as we only do it once. But: blop 3 blop 4 Now Nasm complains about "label_1" (etc.) being redfined! The solution to this is "macro-local" labels... %%label_%+n: Now Nasm generates (use the "-E" switch on the command line to see this): ..&lt; at &gt;0</pre> Frank Kotler 2011-06-19T14:13:26 http://permalink.gmane.org/gmane.comp.lang.nasm.general/315 <pre>Note that recent versions of gas have started to support Intel syntax too. That pseudo-Motorola syntax was indeed an abomination. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay </pre> Jakob Bohm 2011-05-17T08:38:13 http://permalink.gmane.org/gmane.comp.lang.nasm.general/314 <pre> I'll have a look, thanks. Sorry about that! New as I am to Linux development I ASSumed there was only gdb! I've been using stabs but as you and the previous poster said dwarf, I'll start using that instead. Right :-) Good to know. Thank you. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay </pre> Fritz Wuehler 2011-05-16T20:04:30 http://permalink.gmane.org/gmane.comp.lang.nasm.general/313 <pre> Thank you. I finally found a problem was reported on the insight front end to gdb back in 2009 causing a segfault, looks like it was never fixed. So I am using ddd for now, it's not as pretty as insight but it doesn't crash LOL. I finally found where to say Intel format instead of ATT so now I am doing better. I'm so happy about NASM, how can anybody stand to use ATT format or gas? It's a crime against humanity! I will try and remember this. At the moment I'm writing just a few instructions to try and learn and go through the book. I was reading a book that said to use stabs debug info but I will try and see if I can use dwarf and get better results. I am using elf64 format at the moment. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. htt</pre> Anonymous 2011-05-16T15:34:20 http://permalink.gmane.org/gmane.comp.lang.nasm.general/312 <pre> There was recently some discussion of debuggers for Linux on the Nasm Forum: http://forum.nasm.us/index.php?topic=1056.0 You don't say what debugger front end you tried, but ASSuming it's for gdb... 1)It seems to help to start with a "nop" right after the "_start:" label. If you're starting with "main", so that the "_start:" label is elsewhere, this may not help. 2)Give Nasm "-F dwarf" on the command line. The default is "stabs" if you just use the "-g" switch. I honestly don't see any difference, but "dwarf" is the "native" format, and is supposed to be "better". 3) Don't give ld the "-s" switch, of course, or it'll strip the debug info back out. :) 4) Nasm's "local label" syntax doesn't play nicely with gdb. You can use local labels, but don't expect to tell gdb about 'em - it thinks you're trying to reference a member of a structure! If none of that helps, tell us more about exactly what you're doing, and what's happening. Best, Frank --------------------------------------------------</pre> Frank Kotler 2011-05-16T13:59:07 http://permalink.gmane.org/gmane.comp.lang.nasm.general/311 <pre>I have not debugged nasm code on Linux, so I have no specific advice for you, but here are some general info to help you along: Hmm, maybe it is not the nasm format, but the debug information format that is the problem. As on all platforms, there are different file formats that compilers, assemblers etc. can use to tell debuggers which code bytes in the output file correspond to which lines in your source code file and what the name of that file is. In the case of Linux/Unix/GNU tools it may also be mandatory to include NASM directives to mark the beginning and end of each named function, as gdb seems to be overly focused on checking that information before looking at anything real. Anyway, most current Linux tools use the GNU DWARF debug information format, I don't know if NASM includes DWARF information in its elf32 output files. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran deve</pre> Jakob Bohm 2011-05-16T12:06:07 http://permalink.gmane.org/gmane.comp.lang.nasm.general/310 <pre>Hi guys, I am trying to learn x86 assembly with NASM since it uses the less hideous Intel syntax! However the debugger front end I tried doesn't seem to recognize this format and I can't set breakpoints. Whoever is using NASM on Linux can you explain your environment a bit, what tools should I be using etc. for best results. Thanks guys. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay </pre> Fritz Wuehler 2011-05-16T10:57:35 http://permalink.gmane.org/gmane.comp.lang.nasm.general/309 <pre> You might find some of the information on this site useful: http://wiki.osdev.org/Main_Page Good luck! Best, Frank ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d </pre> Frank Kotler 2011-03-09T11:22:15 http://permalink.gmane.org/gmane.comp.lang.nasm.general/308 <pre> Mmmm, no chance of altering files legitimately either, then? Dunno. It "should", if the emulation is correct, I guess. Try it. Seems like it might be the hard way... Try it... no harm done(?) if it doesn't work normally... Best, Frank ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d </pre> Frank Kotler 2011-03-08T22:06:33 http://permalink.gmane.org/gmane.comp.lang.nasm.general/307 <pre> Jeez, I did it myself... ---------------------- kevin becker wrote: &gt; uhm &gt; &gt; when i click on the NASM.exe, it pops upon, and then closes before anything can be even SEEN &gt; &gt; it doesn't do anything.... Ah, okay. Nasm is a "command line" utility. That is, at a "command prompt", you'd type "nasm -f win32 -i c:\my\includes\ -o myfile.obj myfile.asm", or so. You can get a command prompt by doing start-&gt;run-&gt;"cmd" - I think that still works. Alternatively, there's a way to make a "shortcut" to Nasm that will pop up a dialog-box when you click on it that will allow you to enter a command line. I'm afraid I don't remember how that one goes - "properties-&gt;advanced" somewhere, no doubt... Or, you might prefer an "IDE" - an "Integrated Development Environment" which will allow you to clickie-clickie to edit, assemble, run, debug, etc. NaGoA was one created for Nasm. It appears to be "abandoned", but still works, AFAIK. http://www.visual-assembler.pt.vu/ (wow! that's *really* looking abandoned!) </pre> Frank Kotler 2011-03-08T18:52:14 http://permalink.gmane.org/gmane.comp.lang.nasm.general/306 <pre> FUNEM? SIFM. FUNEX? SIFX. OKMNX. (since you've eaten all the waffles...) :) Hi Kevin, I'm not quite clear what "it" is. (like Bill Clinton :) ) Is Nasm quitting on you before it assembles your file? Or is your program exiting before you can see the result? The mention of "system("pause"); sounds like the latter(?). We can call system() from assembly, too, of course. Probably you want to wait for a keystroke(?). How you do that depends on your OS, or if you're linking against a C library, getc()... I think we need more information about exactly what you did, and what happened (as opposed to what you wanted to happen). Best, Frank (Incidentally, click "reply all" to reply to the list - otherwise it goes just to me. I've cleared your "moderation flag", so your message ought to appear right away, this time. Sorry for the delay.) ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview o</pre> Frank Kotler 2011-03-08T13:46:17 http://permalink.gmane.org/gmane.comp.lang.nasm.general/305 <pre>i have ap orblem whenever i try to run it it shuts down instantly. It does the same thing when i run a program in Dev C++, but that i can just type system("PAUSE); please help me thanx </pre> kevin becker 2011-03-08T00:00:06 http://permalink.gmane.org/gmane.comp.lang.nasm.general/304 <pre> Hi Tyler, You're welcome. I'm going to undo your consideration and fill up everybody's mailbox, though, 'cause I think your questions are interesting, and might lead to some discussion. If anyone thinks this list is generating too much traffic, they can complain... or just unsubscribe. :) ASSuming you want to do this via the int 80h interface, there's really only one sys_socketcall (102). This is usually "wrapped" to socket (create), connect, bind, listen, etc. Even Konstantin's "asmutils" provides macros for sys_socket, etc. But the "real" interface is just sys_socketcall, with the subfunctions or "commands" in ebx - ecx points to remaining parameters. In order to not "hide" anything, I like to do it that way, although we're "supposed" to use the C library interface (they make me say that). There are "send" and "recv" commands, but sys_write/sys_read seem to work - sys_close seems to work - just like any other file descriptor. Well, "just call malloc". There are a couple of system calls t</pre> Frank Kotler 2010-12-20T20:36:36 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lang.nasm.general