API tools faq
paste
Advertisement
Guest User

turm0il is a clown

a guest
Feb 19th, 2016
105
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 20.37 KB | None | 0 0
raw download clone embed print report
  1. (02/19/2016 02:51:22 AM) turm0il@jabber.se: fuck otr
  2. (02/19/2016 02:51:22 AM) turm0il@jabber.se: nigga
  3. (02/19/2016 02:51:34 AM) turm0il@jabber.se: still unlocatable
  4. (02/19/2016 03:37:45 AM) turm0il@jabber.se: cant locate a myth
  5. (10:20:14 PM) Attempting to start a private conversation with turm0il@jabber.se...
  6. (10:20:29 PM) turm0il@jabber.se: fuck otr
  7. (10:20:31 PM) turm0il@jabber.se: nigga
  8. (10:22:39 PM) simple@jabber.se/7110815891455915924809588: hi
  9. (10:22:47 PM) simple@jabber.se/7110815891455915924809588: someone told me you could help me with my x86 homework!
  10. (10:23:00 PM) turm0il@jabber.se: lol
  11. (10:23:13 PM) simple@jabber.se/7110815891455915924809588: can u?
  12. (10:23:20 PM) turm0il@jabber.se: maybe
  13. (10:23:26 PM) simple@jabber.se/7110815891455915924809588: ok, so there's this question here
  14. (10:23:37 PM) simple@jabber.se/7110815891455915924809588: and it's asking me the difference between eip and rip
  15. (10:24:37 PM) simple@jabber.se/7110815891455915924809588: eip is like 64bit right?
  16. (10:24:40 PM) turm0il@jabber.se: EIP is for x86 (32-bit) systems, as it is a 32-bit instruction pointer. RIP is for x86_64 (64-bit) as it is a 64-bit instruction pointer.
  17. (10:24:40 PM) simple@jabber.se/7110815891455915924809588: and rip is 32?
  18. (10:24:51 PM) simple@jabber.se/7110815891455915924809588: ah!
  19. (10:24:52 PM) turm0il@jabber.se: EIP = 32 bit, RIP = 64 bit
  20. (10:25:00 PM) simple@jabber.se/7110815891455915924809588: then what the fuq is IP?
  21. (10:25:15 PM) turm0il@jabber.se: Instruction pointer memory addresses point to a line of code (ASM)
  22. (10:25:19 PM) turm0il@jabber.se: For example
  23. (10:25:21 PM) turm0il@jabber.se: if we have
  24. (10:25:21 PM) simple@jabber.se/7110815891455915924809588: ya
  25. (10:25:23 PM) simple@jabber.se/7110815891455915924809588: but like
  26. (10:25:29 PM) turm0il@jabber.se: 0x1234 and it points to somthing like
  27. (10:25:31 PM) simple@jabber.se/7110815891455915924809588: what architecture is ip?
  28. (10:25:35 PM) simple@jabber.se/7110815891455915924809588: basically
  29. (10:25:35 PM) turm0il@jabber.se: oh
  30. (10:25:37 PM) simple@jabber.se/7110815891455915924809588: it's asking me
  31. (10:25:41 PM) simple@jabber.se/7110815891455915924809588: to explain the diff between ip
  32. (10:25:41 PM) simple@jabber.se/7110815891455915924809588: eip
  33. (10:25:42 PM) simple@jabber.se/7110815891455915924809588: and rip
  34. (10:25:57 PM) turm0il@jabber.se: IP might be 16 bit, Im not that good at this shit lmfao
  35. (10:26:13 PM) simple@jabber.se/7110815891455915924809588: ok
  36. (10:26:15 PM) simple@jabber.se/7110815891455915924809588: sec
  37. (10:26:18 PM) simple@jabber.se/7110815891455915924809588: lemme write that down
  38. (10:26:26 PM) turm0il@jabber.se: "turm0il is not good at this shit"
  39. (10:26:33 PM) simple@jabber.se/7110815891455915924809588: k
  40. (10:26:35 PM) simple@jabber.se/7110815891455915924809588: it asks me
  41. (10:26:39 PM) simple@jabber.se/7110815891455915924809588: what a register is
  42. (10:27:08 PM) turm0il@jabber.se: A register is just like a container, it holds data.
  43. (10:27:36 PM) simple@jabber.se/7110815891455915924809588: oh
  44. (10:28:08 PM) turm0il@jabber.se: EAX is a register, so is AL, the difference is that EAX is meant for 32 bit and AL is 8 bit
  45. (10:28:19 PM) turm0il@jabber.se: You have many registers that hold shit on one machine
  46. (10:28:26 PM) turm0il@jabber.se: if you didnt already know that lmfaooo
  47. (10:29:05 PM) simple@jabber.se/7110815891455915924809588: i did not
  48. (10:29:07 PM) simple@jabber.se/7110815891455915924809588: ok
  49. (10:29:08 PM) simple@jabber.se/7110815891455915924809588: now it asks me
  50. (10:29:16 PM) simple@jabber.se/7110815891455915924809588: for 2 ways
  51. (10:29:19 PM) simple@jabber.se/7110815891455915924809588: to clear a register
  52. (10:29:27 PM) simple@jabber.se/7110815891455915924809588: and the advantages
  53. (10:29:28 PM) simple@jabber.se/7110815891455915924809588: of each one
  54. (10:30:30 PM) turm0il@jabber.se: Tbh you're asking the wrong person, as I said Im not too good with this. Btw, for someone just learning basics, why do you need to know how to clear one? Im having a hard time believing you're here for any other purpose than to test me ;P
  55. (10:30:45 PM) simple@jabber.se/7110815891455915924809588: i'm not sure man
  56. (10:30:47 PM) simple@jabber.se/7110815891455915924809588: it asks me
  57. (10:30:51 PM) simple@jabber.se/7110815891455915924809588: how to clear a register
  58. (10:30:57 PM) turm0il@jabber.se: In ASM?
  59. (10:30:59 PM) simple@jabber.se/7110815891455915924809588: yep
  60. (10:31:08 PM) simple@jabber.se/7110815891455915924809588: wait..
  61. (10:31:14 PM) simple@jabber.se/7110815891455915924809588: php..
  62. (10:31:14 PM) simple@jabber.se/7110815891455915924809588: nope
  63. (10:31:16 PM) simple@jabber.se/7110815891455915924809588: idk
  64. (10:31:19 PM) simple@jabber.se/7110815891455915924809588: PHP
  65. (10:31:21 PM) simple@jabber.se/7110815891455915924809588: i think
  66. (10:31:30 PM) turm0il@jabber.se: <?php?>
  67. (10:31:33 PM) turm0il@jabber.se: whoops
  68. (10:31:51 PM) simple@jabber.se/7110815891455915924809588: coming to think of it, what the fuq is a register in php?
  69. (10:32:34 PM) simple@jabber.se/7110815891455915924809588: man im confused
  70. (10:32:34 PM) turm0il@jabber.se: <?php
  71. $variable = 'string'; // placed in register
  72. $variable2 = 'string'; // placed in different register
  73. $variable = NULL;
  74. ?>
  75. (10:32:42 PM) turm0il@jabber.se: $variable2 = NULL;
  76. (10:32:48 PM) simple@jabber.se/7110815891455915924809588: whoa
  77. (10:32:50 PM) simple@jabber.se/7110815891455915924809588: wtf
  78. (10:32:55 PM) simple@jabber.se/7110815891455915924809588: NULL?
  79. (10:33:00 PM) turm0il@jabber.se: place a string in a register and then replace the value in the register with a NULL value
  80. (10:33:12 PM) turm0il@jabber.se: NULL = unknown/none
  81. (10:33:17 PM) simple@jabber.se/7110815891455915924809588: so a register is a variable?
  82. (10:33:20 PM) simple@jabber.se/7110815891455915924809588: in php
  83. (10:33:49 PM) turm0il@jabber.se: Idk, Im assuming that the variable values are held in registers
  84. (10:33:51 PM) turm0il@jabber.se: lmfao
  85. (10:33:53 PM) turm0il@jabber.se: makes sense to me
  86. (10:34:00 PM) simple@jabber.se/7110815891455915924809588: right ok
  87. (10:34:03 PM) simple@jabber.se/7110815891455915924809588: sec
  88. (10:35:17 PM) simple@jabber.se/7110815891455915924809588: OK
  89. (10:35:19 PM) simple@jabber.se/7110815891455915924809588: ALMOST DONE
  90. (10:35:37 PM) simple@jabber.se/7110815891455915924809588: mov eax, 1
  91. mov ebx, 0
  92. int 80h
  93. (10:35:41 PM) simple@jabber.se/7110815891455915924809588: it asks me
  94. (10:35:43 PM) simple@jabber.se/7110815891455915924809588: to explain that code
  95. (10:36:03 PM) turm0il@jabber.se: Then explain it
  96. (10:36:08 PM) simple@jabber.se/7110815891455915924809588: what is it
  97. (10:36:11 PM) simple@jabber.se/7110815891455915924809588: though
  98. (10:36:12 PM) simple@jabber.se/7110815891455915924809588: idk
  99. (10:36:13 PM) simple@jabber.se/7110815891455915924809588: what the fuq
  100. (10:36:14 PM) simple@jabber.se/7110815891455915924809588: it does
  101. (10:36:27 PM) simple@jabber.se/7110815891455915924809588: looks arabic 2 me
  102. (10:36:37 PM) turm0il@jabber.se: This whole time Im just doing your homework? ;P Im still not believing it
  103. (10:36:42 PM) simple@jabber.se/7110815891455915924809588: holy fuck
  104. (10:36:47 PM) simple@jabber.se/7110815891455915924809588: i just turned the page over
  105. (10:36:50 PM) simple@jabber.se/7110815891455915924809588: hoooly fuck
  106. (10:36:56 PM) simple@jabber.se/7110815891455915924809588: push?
  107. (10:36:57 PM) simple@jabber.se/7110815891455915924809588: pop?
  108. (10:37:01 PM) simple@jabber.se/7110815891455915924809588: man im getting confused wtf
  109. (10:37:05 PM) simple@jabber.se/7110815891455915924809588: ok
  110. (10:37:09 PM) simple@jabber.se/7110815891455915924809588: mov eax, 1
  111. (10:37:16 PM) simple@jabber.se/7110815891455915924809588: hmm
  112. (10:37:37 PM) simple@jabber.se/7110815891455915924809588: help?
  113. (10:37:55 PM) turm0il@jabber.se: No
  114. (10:37:56 PM) turm0il@jabber.se: Like I said
  115. (10:37:58 PM) turm0il@jabber.se: Im the wrong person
  116. (10:38:51 PM) simple@jabber.se/7110815891455915924809588: why?
  117. (10:38:52 PM) simple@jabber.se/7110815891455915924809588: wtf
  118. (10:38:59 PM) turm0il@jabber.se: Who sent you?
  119. (10:39:01 PM) simple@jabber.se/7110815891455915924809588: dude
  120. (10:39:06 PM) simple@jabber.se/7110815891455915924809588: can u help me or not
  121. (10:39:07 PM) simple@jabber.se/7110815891455915924809588: plz
  122. (10:39:54 PM) simple@jabber.se/7110815891455915924809588: dude u were doing good
  123. (10:40:03 PM) turm0il@jabber.se: I
  124. (10:40:05 PM) turm0il@jabber.se: W
  125. (10:40:06 PM) turm0il@jabber.se: A
  126. (10:40:07 PM) turm0il@jabber.se: S
  127. (10:40:14 PM) simple@jabber.se/7110815891455915924809588: i know u were
  128. (10:40:18 PM) simple@jabber.se/7110815891455915924809588: help me
  129. (10:40:18 PM) simple@jabber.se/7110815891455915924809588: ffs
  130. (10:40:33 PM) turm0il@jabber.se: H
  131. (10:40:48 PM) simple@jabber.se/7110815891455915924809588: ??
  132. (10:40:50 PM) simple@jabber.se/7110815891455915924809588: fk this
  133. (10:40:57 PM) turm0il@jabber.se: lmfao
  134. (10:41:25 PM) turm0il@jabber.se: http://www.tutorialspoint.com/assembly_programming/assembly_addressing_modes.htm
  135.  
  136. Why dont you do some studying and try to answer the problem yourself? You arent going to learn anything from me giving you every answer.
  137. (10:41:54 PM) simple@jabber.se/7110815891455915924809588: i am dude
  138. (10:41:55 PM) simple@jabber.se/7110815891455915924809588: so far
  139. (10:41:56 PM) simple@jabber.se/7110815891455915924809588: i know
  140. (10:41:59 PM) simple@jabber.se/7110815891455915924809588: a register
  141. (10:42:01 PM) simple@jabber.se/7110815891455915924809588: is a container
  142. (10:42:08 PM) simple@jabber.se/7110815891455915924809588: the diff between
  143. (10:42:09 PM) simple@jabber.se/7110815891455915924809588: ip
  144. (10:42:11 PM) simple@jabber.se/7110815891455915924809588: eip
  145. (10:42:11 PM) simple@jabber.se/7110815891455915924809588: rip
  146. (10:42:41 PM) simple@jabber.se/7110815891455915924809588: ok
  147. (10:42:43 PM) simple@jabber.se/7110815891455915924809588: can u help me
  148. (10:42:46 PM) simple@jabber.se/7110815891455915924809588: with 1 more question
  149. (10:44:38 PM) turm0il@jabber.se: https://www.youtube.com/watch?v=RqViXrPTDM8
  150. (10:44:45 PM) turm0il@jabber.se: That might help you address you last one as well
  151. (10:45:30 PM) simple@jabber.se/7110815891455915924809588: eh?
  152. (10:45:31 PM) simple@jabber.se/7110815891455915924809588: mov?
  153. (10:45:33 PM) simple@jabber.se/7110815891455915924809588: the last one
  154. (10:45:33 PM) simple@jabber.se/7110815891455915924809588: is
  155. (10:45:47 PM) simple@jabber.se/7110815891455915924809588: xor eax, eax
  156. (10:45:49 PM) simple@jabber.se/7110815891455915924809588: what does this do
  157. (10:46:16 PM) turm0il@jabber.se: https://www.youtube.com/watch?v=eUH-mfp_5BM
  158.  
  159. ;P
  160. (10:48:49 PM) simple@jabber.se/7110815891455915924809588: k
  161. (10:48:50 PM) simple@jabber.se/7110815891455915924809588: final 1
  162. (10:48:56 PM) simple@jabber.se/7110815891455915924809588: where is the heap stored?
  163. (10:49:10 PM) turm0il@jabber.se: Jesus christ dude lmfao
  164. (10:49:16 PM) simple@jabber.se/7110815891455915924809588: ???
  165. (10:49:19 PM) simple@jabber.se/7110815891455915924809588: what
  166. (10:49:26 PM) turm0il@jabber.se: There is no way you're donig assembly programming and dont understand "where" the heap is stored
  167. (10:49:30 PM) turm0il@jabber.se: Where do you think?
  168. (10:49:35 PM) simple@jabber.se/7110815891455915924809588: in my computer?
  169. (10:49:39 PM) turm0il@jabber.se: What is the heap?
  170. (10:49:50 PM) simple@jabber.se/7110815891455915924809588: idk..
  171. (10:49:56 PM) turm0il@jabber.se: Lmfaooo
  172. (10:50:02 PM) simple@jabber.se/7110815891455915924809588: dude it's not funny
  173. (10:50:05 PM) simple@jabber.se/7110815891455915924809588: i'm trying to learn
  174. (10:50:43 PM) simple@jabber.se/7110815891455915924809588: fine
  175. (10:50:45 PM) turm0il@jabber.se: Heap is a memory type, I suppose you could say. Stack is a memory type, the difference is how they both function and work but there are pros and cons to each.
  176. (10:51:16 PM) turm0il@jabber.se: Memory is stored into your RAM, unless all your RAM is allocated, in which case it will use open space on your HDD/SSD
  177. (10:51:20 PM) turm0il@jabber.se: If I remember correctly that is
  178. (10:51:30 PM) simple@jabber.se/7110815891455915924809588: so the heap is stored in RAM?
  179. (10:51:37 PM) turm0il@jabber.se: Yes
  180. (10:51:44 PM) simple@jabber.se/7110815891455915924809588: ok
  181. (10:52:04 PM) simple@jabber.se/7110815891455915924809588: i always thought the heap
  182. (10:52:08 PM) simple@jabber.se/7110815891455915924809588: was a data structure
  183. (10:52:10 PM) simple@jabber.se/7110815891455915924809588: almost like a buffer
  184. (10:52:15 PM) simple@jabber.se/7110815891455915924809588: idk
  185. (10:53:09 PM) turm0il@jabber.se: lmfao
  186. (10:53:10 PM) turm0il@jabber.se: a buffer
  187. (10:53:13 PM) turm0il@jabber.se: and data structure
  188. (10:53:17 PM) turm0il@jabber.se: are two completely different things
  189. (10:53:21 PM) simple@jabber.se/7110815891455915924809588: i see ok
  190. (10:53:24 PM) turm0il@jabber.se: but yes, it is a data structure
  191. (10:53:33 PM) simple@jabber.se/7110815891455915924809588: i thought it was a memory type though?
  192. (10:53:34 PM) simple@jabber.se/7110815891455915924809588: wtf
  193. (10:53:44 PM) turm0il@jabber.se: lol my weird wording will throw you the fuck off
  194. (10:53:51 PM) turm0il@jabber.se: I already said Im not the one to ask
  195. (10:53:52 PM) turm0il@jabber.se: but
  196. (10:54:28 PM) turm0il@jabber.se: stack = data structure, heap = data structure. There are two types of memory that programs will use, that is stack or heap. The difference is the structure of each
  197. (10:54:30 PM) turm0il@jabber.se: for instance
  198. (10:55:22 PM) turm0il@jabber.se: Imagine a stack of books. This can represent the stack. Each book can hold data
  199. (10:55:39 PM) turm0il@jabber.se: a stack pointer will always point to the top of a stack
  200. (10:55:44 PM) simple@jabber.se/7110815891455915924809588: ok
  201. (10:55:54 PM) simple@jabber.se/7110815891455915924809588: so the stack pointer is static?
  202. (10:55:54 PM) turm0il@jabber.se: meaning when you reference the stack it will return the item at the top
  203. (10:56:02 PM) turm0il@jabber.se: Yes
  204. (10:56:34 PM) simple@jabber.se/7110815891455915924809588: ok
  205. (10:56:38 PM) turm0il@jabber.se: The heap can be represented by a book shelf. Books up and down, left and right. Like a grid I suppose. Its larger than the stack
  206. (10:56:46 PM) turm0il@jabber.se: Im not too familiar with the heap though
  207. (10:56:52 PM) turm0il@jabber.se: Soooo
  208. (10:57:02 PM) simple@jabber.se/7110815891455915924809588: so like
  209. (10:57:06 PM) simple@jabber.se/7110815891455915924809588: what's the purpose
  210. (10:57:07 PM) simple@jabber.se/7110815891455915924809588: of the sp?
  211. (10:57:23 PM) simple@jabber.se/7110815891455915924809588: surely it just doesn't
  212. (10:57:24 PM) simple@jabber.se/7110815891455915924809588: sit there
  213. (10:57:33 PM) simple@jabber.se/7110815891455915924809588: does it point
  214. (10:57:37 PM) simple@jabber.se/7110815891455915924809588: to something?
  215. (10:57:38 PM) simple@jabber.se/7110815891455915924809588: or
  216. (10:57:39 PM) simple@jabber.se/7110815891455915924809588: ??
  217. (10:57:39 PM) simple@jabber.se/7110815891455915924809588: idk
  218. (10:58:18 PM) turm0il@jabber.se: Hm this is a bit harder to explain. When you call the stack, it calls the pointer. The pointer will look at the stack and see what item is sitting at the top.
  219. (10:58:38 PM) turm0il@jabber.se: I didnt really understand it at first either, its sorta something I have just accepted. It "sits" there
  220. (10:58:51 PM) simple@jabber.se/7110815891455915924809588: hmm..
  221. (10:58:56 PM) simple@jabber.se/7110815891455915924809588: so
  222. (10:58:58 PM) simple@jabber.se/7110815891455915924809588: the stack is LIFO
  223. (10:58:59 PM) simple@jabber.se/7110815891455915924809588: but
  224. (10:59:03 PM) simple@jabber.se/7110815891455915924809588: it just sits there?
  225. (10:59:23 PM) simple@jabber.se/7110815891455915924809588: if it always pointed to the top, wouldn't it store like
  226. (10:59:32 PM) simple@jabber.se/7110815891455915924809588: the address of the last program request?
  227. (10:59:56 PM) turm0il@jabber.se: ah, this is where stack frames come into play
  228. (11:00:02 PM) simple@jabber.se/7110815891455915924809588: ok
  229. (11:01:13 PM) turm0il@jabber.se: and the entrance of a program, if it doesnt use heap memory, it gets a stack frame. In this frame is its stack, it holds stack items in the stack frame. Each program will reference a different stack frame assuming stack memory is teh structure type is uses
  230. (11:01:27 PM) turm0il@jabber.se: the stack pointer will always point to the top of its stack frame
  231. (11:01:33 PM) turm0il@jabber.se: Got it?
  232. (11:01:46 PM) simple@jabber.se/7110815891455915924809588: sure
  233. (11:01:49 PM) simple@jabber.se/7110815891455915924809588: so i would be wrong in saying
  234. (11:01:52 PM) simple@jabber.se/7110815891455915924809588: sp
  235. (11:01:59 PM) simple@jabber.se/7110815891455915924809588: holds the last program requests's address
  236. (11:02:10 PM) turm0il@jabber.se: Yeah you would
  237. (11:02:35 PM) simple@jabber.se/7110815891455915924809588: damn ok..
  238. (11:02:35 PM) turm0il@jabber.se: SP references the item at the top of the stack within a stack frame.
  239. (11:02:55 PM) simple@jabber.se/7110815891455915924809588: but man i'm not getting this homie
  240. (11:02:58 PM) simple@jabber.se/7110815891455915924809588: if the stack is LIFO
  241. (11:03:08 PM) simple@jabber.se/7110815891455915924809588: how can the sp
  242. (11:03:12 PM) simple@jabber.se/7110815891455915924809588: not point to the last address
  243. (11:03:13 PM) simple@jabber.se/7110815891455915924809588: used
  244. (11:03:15 PM) simple@jabber.se/7110815891455915924809588: in the program
  245. (11:03:20 PM) simple@jabber.se/7110815891455915924809588: if it's always pointing to the top of the stack?
  246. (11:04:20 PM) turm0il@jabber.se: Its up to the program/programmer to move items around within the stack in order to reference them using the stack pointer. If item is larger than item2, move to top of stack, call function with stack pointer as argument
  247. (11:04:44 PM) turm0il@jabber.se: therefore item is referenced rather than whatever was left at the top
  248. (11:05:17 PM) simple@jabber.se/7110815891455915924809588: ok..
  249. (11:05:20 PM) simple@jabber.se/7110815891455915924809588: so
  250. (11:05:27 PM) simple@jabber.se/7110815891455915924809588: this could basically mean
  251. (11:05:32 PM) simple@jabber.se/7110815891455915924809588: pushing a register
  252. (11:05:37 PM) simple@jabber.se/7110815891455915924809588: onto a stack
  253. (11:05:42 PM) simple@jabber.se/7110815891455915924809588: could make it random
  254. (11:05:45 PM) simple@jabber.se/7110815891455915924809588: and not always at the top?
  255. (11:06:18 PM) simple@jabber.se/7110815891455915924809588: because of the stack frame?
  256. (11:06:19 PM) turm0il@jabber.se: It would be pushing an item into a register held within the stack, but it would place it at the top I think
  257. (11:06:22 PM) turm0il@jabber.se: ahain
  258. (11:06:24 PM) turm0il@jabber.se: again*
  259. (11:06:27 PM) turm0il@jabber.se: Im the wrong person
  260. (11:06:35 PM) simple@jabber.se/7110815891455915924809588: wait
  261. (11:06:38 PM) simple@jabber.se/7110815891455915924809588: so we would be pushing
  262. (11:06:39 PM) simple@jabber.se/7110815891455915924809588: a register
  263. (11:06:40 PM) simple@jabber.se/7110815891455915924809588: into a register
  264. (11:06:43 PM) simple@jabber.se/7110815891455915924809588: on the stack?
  265. (11:06:47 PM) turm0il@jabber.se: No
  266. (11:06:50 PM) turm0il@jabber.se: we push data into a register
  267. (11:06:54 PM) turm0il@jabber.se: and that register
  268. (11:06:57 PM) turm0il@jabber.se: is held in the stack
  269. (11:07:01 PM) simple@jabber.se/7110815891455915924809588: i see
  270. (11:07:01 PM) simple@jabber.se/7110815891455915924809588: ok
  271. (11:08:52 PM) simple@jabber.se/7110815891455915924809588: so
  272. (11:08:55 PM) simple@jabber.se/7110815891455915924809588: u can't push
  273. (11:08:56 PM) simple@jabber.se/7110815891455915924809588: REGISTERS
  274. (11:08:58 PM) simple@jabber.se/7110815891455915924809588: onto the stack?
  275. (11:09:11 PM) turm0il@jabber.se: No I dont think so lmfao
  276. (11:09:17 PM) simple@jabber.se/7110815891455915924809588: damn ok
  277. (11:10:04 PM) simple@jabber.se/7110815891455915924809588: so like
  278. (11:10:06 PM) simple@jabber.se/7110815891455915924809588: what the fuck
  279. (11:10:36 PM) simple@jabber.se/7110815891455915924809588: hmm
  280. (11:11:13 PM) simple@jabber.se/7110815891455915924809588: so i'm wrong in sayin
  281. (11:11:20 PM) simple@jabber.se/7110815891455915924809588: a stack is a storage area?
  282. (11:11:23 PM) simple@jabber.se/7110815891455915924809588: and is rather a memory type
  283. (11:11:36 PM) turm0il@jabber.se: Yes
  284. (11:11:45 PM) simple@jabber.se/7110815891455915924809588: DAMN OK HOMIE
  285. (11:12:02 PM) turm0il@jabber.se: More of a structure type to hold memory tho imo
  286. (11:12:04 PM) turm0il@jabber.se: But
  287. (11:12:11 PM) turm0il@jabber.se: you can get away with saying it is a memory type
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!