| |
| |
| |
|
Page: 1 2
Comments:
<0> I440r: you have an ARM development kit?
<1> yes
<1> oh
<0> was it free
<1> u mean the hardware. no
<1> hell no
<0> ah ok
<0> :(
<1> i have the development suite - and that surely aint free :)
<0> ah
<0> I have arm access on my palmOS thru OBC but there is no real good documentation out there
<1> try #gbadev and #dsdev on irc.blitzed.org. they can help you do arm devel :)
<0> I440r: I have inlineAsmwithOnBoardC if you want it
<1> cant use onboard c
<1> this is at work
<1> ads 1.2
<2> hi
<3> hi there, is it possible to modify stack memory with gdb?
<4> pi-cubic: yes
<4> pi-cubic: ((int*)$esp)[4] = 42;
<4> without ";" i think
<5> hey
<6> Mornin
<5> whats new?
<6> Just wakin' up
<6> And working with a newbie to AC in ##electronics. sameo' sameo'
<5> heh fair enough :p
<5> you into ***embly too I hope? :p
<6> lol
<6> Nah, I just can't spell #***
<5> what??? :)
<5> rofl
<5> you're strange :p
<6> haha
<6> I *love* ***embly. I'm a defacto expert in OS/390 and 80x86 (although I'm discovering these days that Intel is adding instructions and I'm not really following the 80x86 ***embly language any more)
<6> I recently learned AVR ***embly. Never really done a RISC platform before
<6> Pretty cool, although kind of odd that half of the instructions only work with half of the registers
<5> ah heh ok
<6> I've been a programmer (sort of) for 17 years. Started my career at a shop that was exclusively mainframe ***embler. Moved into mainframe systems programming (which is why I said "sort of")
<7> try PIC next, just as obscure
<6> lol
<6> Somehow I managed to select AVR instead of PIC. I should probably try it just to have the knowledge
<5> <had been a bit into basic ***embly for a while but now trying to figure some more about compiling/etc since there's one source I'm looking to rebuild for myself
<6> ***embling/linking is pretty easy, especially on Linux
<8> I love linu
<8> x
<6> I use Linux exclusively at home. I use M$ only at work
<5> <is bsd/mac with occ***ional windows mainly for cd games
<5> tried linux ughh I think 3 or 4 times...never liked it but meh
<5> bsd seem a lot friendly to me (and much less downloads demanding -_-)
<8> bsd rules too
<9> anyone here know whether there is a problem with the cpu directive when using NASM?
<9> the manual states that I can say stuff like "cpu 8086" and have it restrict me to the 8086 instruction set
<9> but when compiling, it just says "instruction expected" on that line.
<10> suiraM: ummm? works for me...
<10> surrounding lines?
<9> hmm
<9> before: ;;;;;;;;;;;;;;;;;;;;;
<9> after: %include "config.asm"
<10> config.asm begins with?
<9> ;;;;
<9> nasm version 0.98bf for windows, by the way.
<10> wrong line end markings or what?
<9> compiles fine without this line
<9> config.asm contains only %define's.
<9> and comments
<9> crlf line termination
<10> compiles fine here, still
<10> "cpu 8086"
<9> hmm
<9> wierd
<10> NASM version 0.98.38 compiled on May 17 2005
<6> Is it column specific? Has to be in column 1, or 16, or whatever? And you're not forgetting something stupid the compiler wants, right? Like a period? (gas likes .directive)
<9> I tried a file containing "bits 16\ncpu 8086\n" now
<10> djlogan: nasm doesn't give a **** about whitespace
<9> fails same way
<10> compiles cleanly here
<10> old nasm?
<6> ok. Usually compilers/***emblers use a specific character to mark directives as opposed to instructions.
<9> nasm version 0.98bf for windows
<10> djlogan: fun fact: nasm doesn't.
<10> hmm... though...
<10> "[cpu 8086]"?
<9> hmm
<6> lol mwk -- gotta love it
<11> does someone uses IDA pro?
<12> If you use it, then the answer would be yes
<13> someone does i bet
<6> Do I win? :)
<11> well, my question is: how to start to dis***emble a program by his real entry point? i always lost my way in the program's stubs
<9> unrecognized directive [cpu]
<10> old version, then
<9> hmm... sf out of date?
<14> hello all, I tried C channel the the other day but they said you might have more info here
<10> suiraM: i somehow have 0.98.38
<9> win32
<9> ?
<14> its about /proc/sys/kernel/randomize_va_sp I am trying to overflow a buffer but because randomization is activated, I cannot "guess" the proper address to return the pointer too... anyone knows how to overcome this problem?
<10> no, linux
<10> but... ftp://ftp.kernel.org/pub/software/devel/nasm/binaries/win32/
<10> newest version here is 0.98.39
<9> k
<9> thanks
<9> doesn't work with 0.98.38 here
<9> from kernel.org
<15> hello suiraM
<15> hi mwk
<10> hi
<9> hi smg
<9> mwk- obtw; sorry about not having had time to fire off that mail yet.
<10> suiraM: np, same on this side
<9> mwk- np here too. been a bit busy lately.
<9> mwk- any chance you'd like to try compiling the code with your linux copy of nasm?
<9> mwk- I'd like to find out whether I've done any non-8086 stuff in there without having to go through all the work of manually checking each instruction, so the CPU directive would've been real handy.
<9> mwk- and kernel.org only had 0.98.38, which didn't do the trick.
<10> suiraM: sure. what file?
<9> I'll put it on pastebin
<9> no, wait...
<9> I just ****ed up the unarchiving.
<9> :P
<9> stupid winrar :P
<9> bbl
<15> quit ("Time left until the Apocalypse: 31yrs 1wk 3days 11hrs 13mins 55secs")
<15> why?
<7> watch him over time and it is counting down
<15> yes, but why does he think auf apocalypse in 31yrs?
<7> ask him I dunno
<16> http://en.wikipedia.org/wiki/Year_2038_problem
<17> smg: you will die when that day comes
<17> smg: here is your answer : http://www.acc.umu.se/~zqad/cats/1166518423-HWJKETFIYWTO3CNCCWVNX2VUCNNXXHFP.jpg
<18> 12/21/12 :P
<18> LOL
<18> that pic is pretty funny
<17> yeah
<18> if only rape was spelled right
<17> thats part of teh funny!
<18> oh.. lol
<15> what a **** :P
<7> y2k only better
<15> I hate this people :P
<15> maybe he is jehova?
<19> http://rafb.net/p/AZMsAt95.html can someone help me to understand this code?
<10> ask ASIM.
<10> um... wait, nevermind.
<10> well, t'is setup for self-modifying code, probably
<19> do you know any site where I can read more about all that?
<19> I'm unable to find something useful with google that would cover such code
<10> you're expected to decode it yourself.
<10> there's no good info on self-modifying codde
<20> hi, have anyone masm? (not masm32)
<4> lutifer: is that proprietary?
Return to
#asm
or
Go to some related
logs:
Public key for madwifi is not installed
#kde
#web
#suse
Glob.so: ELF file OS ABI invalid
find_free_number %e is deprecated
GhostlyDeath
#perl
#fluxbox
why linu8x?
|
|
