| |
| |
| |
|
Page: 1 2
Comments:
<0> erm
<0> why does the nasm get an error if iv mov eax, bx?
<1> different operand-size?
<2> cause eax is 32-bit
<2> and bx is 16-bit
<2> movzx does unsigned 16-to-32 conversion, which could be what you want
<2> movsx does signed 16-to-32 conversion
<0> wait
<0> I did movzx ebx, bx
<0> and then
<0> mov eax, bx
<2> wtf?
<0> ah wrong
<0> movzx ebx, bx and mov eax, ebx should be right
<2> why not 'movzx eax, bx'?
<0> oh
<0> this is better =)
<0> mwk: thank you
<0> where is the other guy we talked yesterday?
<2> suiraM? dunno.
<0> hehe
<0> !seen suiraM
<0> let's do an irc bot in asm. lol
<2> 05:27 -!- suiraM [n=suiraM@182.80-203-49.nextgentel.com] has quit ["ircII EPIC4-2.2 -- Are we there yet? (EPIC4-Win32 - http://www.sosdg.org/software.php)";]
<2> enough?
<0> indeed :)
<0> mwk: but you are also nice
<0> mwk: ! :)
<0> btw how can I get a positive value of -5?
<0> I tried mov eax, -5
<0> NEG eax
<0> but won't work
<2> positive value?
<0> yeah get from -5 => 5
<2> neg eax
<0> no :)
<0> oh it worked I mised a ";" :)
<3> hi. can someone give me a tip about the "default" comment character(s) in .s files? is it // or # or ; ?
<2> depends on architecture
<2> according to as infofile, section 3.3:
<2> Anything from the "line comment" character to the next newline is
<2> considered a comment and is ignored. The line comment character is `;'
<2> on the ARC; `@' on the ARM; `;' for the H8/300 family; `;' for the HPPA;
<2> `#' on the i386 and x86-64; `#' on the i960; `;' for the PDP-11; `;'
<2> for picoJava; `#' for Motorola PowerPC; `!' for the Renesas / SuperH SH;
<2> `!' on the SPARC; `#' on the ip2k; `#' on the m32c; `#' on the m32r;
<2> `|' on the 680x0; `#' on the 68HC11 and 68HC12; `#' on the Vax; `;' for
<2> the Z80; `!' for the Z8000; `#' on the V850; `#' for Xtensa systems;
<2> see *Note Machine Dependencies::.
<3> and what about PowerPC64, it would be #?
<2> sure
<3> mwk: thanks a lot!
<2> also, note that IA64 has // comments
<2> which this manual doesn't mention
<3> mwk: where did you get this information?
<3> heh..
<3> should read what you are writing ^^
<3> from as infofile ^^
<3> thanks
<0> EEMOTICONABUSE
<0> mwk: still present
<2> mhm
<0> mwk: you are coding in nasm?
<2> no, i'm browsing bash.org
<0> oh well
<0> HAPPY new DAY :)
<0> hello
<0> salut! :)
<0> what does jnc stand for jump not carry?
<4> yes
<0> this means CF == 0?
<4> yes
<0> thx
<0> and what does edcba stand for? :)
<5> any idea how to force objdump to do a dis***embly even if i don't have any known header in the file? (just looking at a firmware image, i'm ***uming the architecture is arm)
<5> "objdump -z --reloc -D -b binary -m arm"
<0> arm?
<5> yep
<0> what's this? :)
<5> oh, nothing :)
<5> at least not http://en.wikipedia.org/wiki/Nokia_M1122
<0> c'mon, tell me :)
<0> ok
<6> does anybody here know ARM asm?
<7> [BAF64]: Kind of.
<6> hmm
<7> For what cpu? They can be quite different :)
<6> arm7
<7> Coding for the GP2X are we? :-)
<7> brb, I need coffee and smoke
<6> nintendo ds :]
<8> anyone in here use ads 1.2 ?
<7> [BAF64]: Well, state your question.
<6> http://rafb.net/p/yvIc5o30.html <- can you see any reason that code would crash?
<9> yo Madsy you are everywhere
<7> geocalc: yes
<8> i have an ***embler source file that generates about 1000 different symbols.. i cant get any of them to import into the main C comile
<8> im exporting them
<8> but none of them are visible
<7> I440r: Are they extern?
<7> As opposed to static
<8> they are global
<8> theyare just XXX equ some calculated address
<7> And do they follow the cdecl calling convension?
<8> erm xxx equ 123 <-- c CALLING convention ?
<8> how do i make an equ conform to a calling convention
<7> I440r: http://en.wikipedia.org/wiki/Cdecl#Standard_Exit_and_Entry_Sequences_for_C_Code
<9> yo Madsy maybe you know some good site for asm in x86_64 ?
<7> No, sorry.
<7> I'm quite new to ***embly myself.
<9> ahh
<7> The little I know is for the ARM920T cpu.
<7> But if you are in doubt, try wikipedia first.
<9> it's not for me
<7> It usually has some good links.
<9> i tried
<7> Have you visited AMD's pages for documentation?
<9> x86 only
<9> yes too bad
<7> Hm. Strange.
<10> little AT&T syntax question, given: .section .data myint .int 1 , i know using: movl myint, %eax , will move the /value/ 1 into eax, while: movl $myint, %eax , moves 'myint's address. Why then does: movl %eax, myint , work?
<10> shouldn't i need the 'address' in that context?
<11> why would anyone actually what to use at&t syntax
<9> the amd doc say look in intel doc Madsy
<7> lol
<11> lol
<7> Lazy bastards.
<10> because the tools i prefer using, use it.
<12> hello, im writing an emulator of sorts, and im trying to disect a Intel MZ DOS EXE format file, so far i've managed to figure out where all the heads are, and if ive done things correctly, i am pointed to the "Beginning of Execution Code" but whats there is "Requires-Win32" ... which 1) doesnt make since, since i compiled it for 16-bit DOS, and that its a MZ executeable, and further, because thats not an opcode.
<12> so where do i start to start executeing the actual code of the program?
<4> wotsit.org
<12> edcba: i got all that, and i get set to a place where it says "Requires-Win32", not an opcode
<4> so you got it wrong
<12> ... yeah... hints why im here saying that i got it wrong and wondering why.
<4> maybe you inverted cs and ip
<12> what is the CS value?
<12> 16 word offset in load module of the code segment (in paras) ?
<12> i dont know HOW an exe file executes, i mean, i know that it contains asm instructions, and opcodes which are processed to jump around the file image
<12> i dont know what a load segment
<12> i've been at this a week now banging my head against a wall, i just want some help in getting the processing of the exe started
<12> hello, im writing an emulator of sorts, and im trying to disect a Intel MZ DOS EXE format file, so far i've managed to figure out where all the heads are, and if ive done things correctly, i am pointed to the "Beginning of Execution Code" but whats there is "Requires-Win32" ... which 1) doesnt make since, since i compiled it for 16-bit DOS, and that its a MZ executeable, and further, because thats not an opcode.
<13> exe files which start with MZ can be in PE format
<12> hmm
<12> wouldent the first two bytes in the file be PE?
<12> oh
<12> thats what you just said nvm
<14> my new sig
<14> 6A0F66586A6866682F62617366682F62696E6689E368ED096659CD80
<14> I was going to write it in MIPS ***embly, but then I realized that nobody would ever get it...
<14> and it would seem then that nobody in #asm gets it either :P
<15> is that.. /bin/bash?
Return to
#asm
or
Go to some related
logs:
kmod-ndiswrapper 1.10
compiz title bar gone
christina perlvar
gentoo can't load module hw_random
#math
pronounce perl
spca5xx module-assistant
caferadius cf install
debian S36discover line 204 problem
#mysql
|
|