Assembly - Division giving weird result











up vote
1
down vote

favorite
1












I'm using a x86 emulator and I'm trying to write a short program that receives an integer and converts it to binary. However, I run it step by step and check the memory (and the ax register as it is updated) I can see that the ax register evolves as it follows: 14 -> 7 -> 3 -> 32769 (Instead of 1). Why is this happening? I've tried using EAX and ECX instead of ax and cx but it still wont give me the correct result. Am I missing something really obvious?



value: dw 14
binary: dw 0

mov ax,0
mov cx,0
mov dx,0

;CONVERTING 14 TO BINARY
CONVERSION:
mov ax,[valor]
mov cx,2
div cx
push dx
mov [valor],ax
cmp ax,0
jne CONVERSION

pop [binary]









share|improve this question


















  • 1




    You need the mov dx,0 inside the loop.
    – Jester
    Nov 9 at 22:14










  • @Jester: why? (Explaing why would make a good answer.)
    – usr2564301
    Nov 9 at 22:19










  • Your push dx may be executed many more times than you are popping it (only once). Best make sure you pop everything that you push. For this toy program it won't matter -- unkess you are going to try larger values next -- but it's a good general rule to keep in mind for anything larger than this.
    – usr2564301
    Nov 9 at 22:21










  • Adding mov dx,0 to the loop made the div work properly! But I just realized that by doing pop into [binary].. isn't giving me the right result either..!
    – falsekein
    Nov 9 at 22:32










  • We don't really know what you are trying to do. Note that dw 14 is already in binary. Maybe you mean a text representation of zeroes and ones?
    – Jester
    Nov 9 at 22:34















up vote
1
down vote

favorite
1












I'm using a x86 emulator and I'm trying to write a short program that receives an integer and converts it to binary. However, I run it step by step and check the memory (and the ax register as it is updated) I can see that the ax register evolves as it follows: 14 -> 7 -> 3 -> 32769 (Instead of 1). Why is this happening? I've tried using EAX and ECX instead of ax and cx but it still wont give me the correct result. Am I missing something really obvious?



value: dw 14
binary: dw 0

mov ax,0
mov cx,0
mov dx,0

;CONVERTING 14 TO BINARY
CONVERSION:
mov ax,[valor]
mov cx,2
div cx
push dx
mov [valor],ax
cmp ax,0
jne CONVERSION

pop [binary]









share|improve this question


















  • 1




    You need the mov dx,0 inside the loop.
    – Jester
    Nov 9 at 22:14










  • @Jester: why? (Explaing why would make a good answer.)
    – usr2564301
    Nov 9 at 22:19










  • Your push dx may be executed many more times than you are popping it (only once). Best make sure you pop everything that you push. For this toy program it won't matter -- unkess you are going to try larger values next -- but it's a good general rule to keep in mind for anything larger than this.
    – usr2564301
    Nov 9 at 22:21










  • Adding mov dx,0 to the loop made the div work properly! But I just realized that by doing pop into [binary].. isn't giving me the right result either..!
    – falsekein
    Nov 9 at 22:32










  • We don't really know what you are trying to do. Note that dw 14 is already in binary. Maybe you mean a text representation of zeroes and ones?
    – Jester
    Nov 9 at 22:34













up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





I'm using a x86 emulator and I'm trying to write a short program that receives an integer and converts it to binary. However, I run it step by step and check the memory (and the ax register as it is updated) I can see that the ax register evolves as it follows: 14 -> 7 -> 3 -> 32769 (Instead of 1). Why is this happening? I've tried using EAX and ECX instead of ax and cx but it still wont give me the correct result. Am I missing something really obvious?



value: dw 14
binary: dw 0

mov ax,0
mov cx,0
mov dx,0

;CONVERTING 14 TO BINARY
CONVERSION:
mov ax,[valor]
mov cx,2
div cx
push dx
mov [valor],ax
cmp ax,0
jne CONVERSION

pop [binary]









share|improve this question













I'm using a x86 emulator and I'm trying to write a short program that receives an integer and converts it to binary. However, I run it step by step and check the memory (and the ax register as it is updated) I can see that the ax register evolves as it follows: 14 -> 7 -> 3 -> 32769 (Instead of 1). Why is this happening? I've tried using EAX and ECX instead of ax and cx but it still wont give me the correct result. Am I missing something really obvious?



value: dw 14
binary: dw 0

mov ax,0
mov cx,0
mov dx,0

;CONVERTING 14 TO BINARY
CONVERSION:
mov ax,[valor]
mov cx,2
div cx
push dx
mov [valor],ax
cmp ax,0
jne CONVERSION

pop [binary]






assembly x86






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 9 at 22:11









falsekein

61




61








  • 1




    You need the mov dx,0 inside the loop.
    – Jester
    Nov 9 at 22:14










  • @Jester: why? (Explaing why would make a good answer.)
    – usr2564301
    Nov 9 at 22:19










  • Your push dx may be executed many more times than you are popping it (only once). Best make sure you pop everything that you push. For this toy program it won't matter -- unkess you are going to try larger values next -- but it's a good general rule to keep in mind for anything larger than this.
    – usr2564301
    Nov 9 at 22:21










  • Adding mov dx,0 to the loop made the div work properly! But I just realized that by doing pop into [binary].. isn't giving me the right result either..!
    – falsekein
    Nov 9 at 22:32










  • We don't really know what you are trying to do. Note that dw 14 is already in binary. Maybe you mean a text representation of zeroes and ones?
    – Jester
    Nov 9 at 22:34














  • 1




    You need the mov dx,0 inside the loop.
    – Jester
    Nov 9 at 22:14










  • @Jester: why? (Explaing why would make a good answer.)
    – usr2564301
    Nov 9 at 22:19










  • Your push dx may be executed many more times than you are popping it (only once). Best make sure you pop everything that you push. For this toy program it won't matter -- unkess you are going to try larger values next -- but it's a good general rule to keep in mind for anything larger than this.
    – usr2564301
    Nov 9 at 22:21










  • Adding mov dx,0 to the loop made the div work properly! But I just realized that by doing pop into [binary].. isn't giving me the right result either..!
    – falsekein
    Nov 9 at 22:32










  • We don't really know what you are trying to do. Note that dw 14 is already in binary. Maybe you mean a text representation of zeroes and ones?
    – Jester
    Nov 9 at 22:34








1




1




You need the mov dx,0 inside the loop.
– Jester
Nov 9 at 22:14




You need the mov dx,0 inside the loop.
– Jester
Nov 9 at 22:14












@Jester: why? (Explaing why would make a good answer.)
– usr2564301
Nov 9 at 22:19




@Jester: why? (Explaing why would make a good answer.)
– usr2564301
Nov 9 at 22:19












Your push dx may be executed many more times than you are popping it (only once). Best make sure you pop everything that you push. For this toy program it won't matter -- unkess you are going to try larger values next -- but it's a good general rule to keep in mind for anything larger than this.
– usr2564301
Nov 9 at 22:21




Your push dx may be executed many more times than you are popping it (only once). Best make sure you pop everything that you push. For this toy program it won't matter -- unkess you are going to try larger values next -- but it's a good general rule to keep in mind for anything larger than this.
– usr2564301
Nov 9 at 22:21












Adding mov dx,0 to the loop made the div work properly! But I just realized that by doing pop into [binary].. isn't giving me the right result either..!
– falsekein
Nov 9 at 22:32




Adding mov dx,0 to the loop made the div work properly! But I just realized that by doing pop into [binary].. isn't giving me the right result either..!
– falsekein
Nov 9 at 22:32












We don't really know what you are trying to do. Note that dw 14 is already in binary. Maybe you mean a text representation of zeroes and ones?
– Jester
Nov 9 at 22:34




We don't really know what you are trying to do. Note that dw 14 is already in binary. Maybe you mean a text representation of zeroes and ones?
– Jester
Nov 9 at 22:34

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53233910%2fassembly-division-giving-weird-result%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53233910%2fassembly-division-giving-weird-result%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Guess what letter conforming each word

Port of Spain

Run scheduled task as local user group (not BUILTIN)