| |
| |
| |
|
Page: 1 2 3 4
Comments:
<0> re, anyone here familar with fasm macros?
<1> nein
<0> pireau would you take a look?
<0> for any logical errors in a macro?
<1> sure
<2> rofl im getting a seg violation
<0> ty, pastebin.ca/128335
<2> my app is reading from the memory address 0xbaadf00d
<0> good adr
<2> i gotta feed it something else now lol
<2> meh, now i gotta do a traceback in gdb :-/
<1> Quiznos: what are you trynig to do ?
<0> pireau it's the main macro for coding a forth kernel
<1> okay
<1> i can't read it correctly
<1> or I simply don't get what it's doing.
<0> ask a question
<0> or shall i walk you through it?
<1> I think i get it
<0> k
<1> err
<1> no
<1> what does it so ?
<1> do*
<0> ok, foundation: the * after name means `required argument'
<0> `head' is the macro name
<0> label and help are optional macro args
<1> yeah
<1> i got that
<0> local list are macro-locals
<1> that too
<1> hlen = $-hl-1
<1> that i don't get, the rest is okay
<0> ok:
<0> $ == current offset to next put a byte into,
<0> hl is the offset of the counted help string
<1> okay
<0> minus 1 for the count byte
<1> yeah
<0> the count isnt part of the string
<0> kinda like an asciiz null byte
<0> part of but basically ignored for manipulation of string
<1> oki
<1> okay, and what's the problem with it ?
<1> it doesnt declare the strings as you like it ?
<0> i'm asking for peer-review for logical errors
<1> oh !
<1> it looks fine to me
<0> btw, fti, the macro lays out a non-standard structure for a forth word;
<1> okay
<0> usually, the name string is not separated as i wrote it
<0> and there is no help-string
<0> i'm tryin to do what emacs does with elisp help-strings
<1> i don't know what those are.
<0> you've never seen elisp code? god bless you!
<0> heh
<1> i'm probably not the right guy to help you review your code.
<0> if you know asm, you're one of the right guys
<0> :>
<0> pireau ok thanks much for allowing me to esplain, that helps me.
<0> later
<1> yeah, sometimes just saying aloud what you're doing helps in finding bugs.
<0> exactly
<0> be well
<3> hola
<4> how do portable code generators work that convert an intermediate language to asm? (I also asked this in #C)
<2> well, i guess you need lotsa books to find out ;)
<5> if one wanted to start learning ***embly, which arch would be the most valuable to learn, or is that still relative to your interests and needs?
<4> x86
<4> why do you ask at all
<5> well that was my intial thought but when learning something so specific like this, you like to double check
<5> about the free intel books, is there any particular book i should try and get?
<6> all ?
<5> woop, im sure that'd be nice but id like to start out with one book for now
<6> I don't really know which books are you talking about, but imho just read http://tinyurl.com/5kfu6 , and it should give you a nice start, or even more than just a "nice start"
<5> woop, alright then
<5> however, im not too fond of linux
<7> does BIOS ROM have some way to 'detaching' from memory after bootup?
<7> you don't want BIOS taking up memory all the time right?
<4> ouch, that little bit of memory
<7> undesktop: ouch?
<8> does anyone have a link to help me out with bignum stuff in asm?
<4> http://www.swox.com/gmp/
<8> im aware of the existence of gmp , its functions are documented but not how they operate, and looking at the source is a bit overwhelming
<9> Question, Does ***embly language care about what OS is running? Like for example, is INT 21 the same on Linux, Windows, etc ?
<4> just btw... why do you think programs are incompatible on the other OS if the syscalls were the same?
<9> My understanding of things this low level is quite weak, but my idea was that --- there were LIBS that basically had functions that the programs called externally, which did not exist on the other OSs
<9> i.e. windows had functions inside of libs that linux did not have basically
<4> hm no, the syscalls are different too - else you could simply avoid the libs and write portable code this way
<4> on Linux, the syscalls are directly mapped to an int, and on Windows, it's implementation specific and you must use the DLLs
<8> holy ****, i just realized he asked the same question in efnet #asm
<8> i was like, whoa deja vu. but not.
<4> be also asked in #C
<9> You were slow here at first :P I was in a hurry lol
<10> kitty likes it rough
<11> hello there
<11> anyone there
<11> hello?
<11> wtf guys
<12> hi
<12> you are all ***embler?
<11> no, i want to learn it
<11> how about you?
<12> i develop a Operating System in asm, and so i know it pretty good
<11> wow,
<11> what OS, if i may ask
<11> windows?
<12> of course you may, ToasterOS
<12> not yet Windows, but in future i want to go to Microsoft
<11> how old are you?
<11> nice
<12> 15
<11> wtf
<11> ur young
<11> fifteen and already you know ***embly language
<11> that's impressive
<12> why do you want to learn asm?
<12> do you want to write an OS too?
<11> i want to learn it because i want to write virii
<11> you know
<11> but not for harm
<11> just to know it
<4> you don't need no stinking asm to write oses
<11> yes you do!
<12> no you don't
<12> but you need a language
<11> really
<11> what about the kernek
<12> C/C++, ***embler, Object Pascal
<11> kernel
<12> ...
<11> hmmm
<12> i have a modularized Kernel
<4> btw, I also wrote a Java kernel not containing a _single_ line of asm
<12> i think for the Bootloader you need asm
<12> i mean you can use grub
<4> (but there was some machine code in hex in it heh)
<12> or anything like that
<4> yes, maybe the loader was in asm... I hadn't access to that
<12> for what OS?
<11> what irc are you guys using?
<12> Nettalk, in past mirc
<12> why?
<11> cuz mine doesn't work
<11> i'm using some java applet
<4> xchat
<12> hmm
<12> linux^^
<11> i tried visualirc
<11> no , windows
<11> xchat, is that it
Return to
#asm
or
Go to some related
logs:
ubuntu nzbget zlib
gx260 linux panic
#ubuntu
navaburo
ubuntu switch user hang
cpan r update all
dpkg hi
ubuntu cinelerra freezes
biodisiel making
perry bible fellowship thumb war
|
|