flat assembler
Message board for the users of flat assembler.
Index
> Windows > Code does not work under 64 bit Vista Goto page 1, 2 Next |
Author |
|
asmcoder 06 Jul 2009, 16:12
[content deleted]
Last edited by asmcoder on 14 Aug 2009, 14:49; edited 1 time in total |
|||
06 Jul 2009, 16:12 |
|
windwakr 06 Jul 2009, 16:14
You know, I am really getting sick of seeing asmcoders fucking retarded and pointless posts. Seriously, if you would like to "check it out" just go to the fucking website at the top of the code, you dumbass.
Bicyclist, please add code tags to the code, it would look much better. Code: [code] before the code and [/code] after it. |
|||
06 Jul 2009, 16:14 |
|
Bicyclist 06 Jul 2009, 17:12
asmcoder wrote: omfg plz translate it to fasm and get rid of includes so i may check it out... Thanks. I write in assembly using masm as my compiler. It looks like there is quite a bit of difference between masm code and fasm. Take care. |
|||
06 Jul 2009, 17:12 |
|
Bicyclist 06 Jul 2009, 17:37
windwakr wrote: You know, I am really getting sick of seeing asmcoders fucking retarded and pointless posts. Seriously, if you would like to "check it out" just go to the fucking website at the top of the code, you dumbass. “What we see depends mainly on what we look for,” said British statesman John Lubbock (1834–1913). A good attitude and the right focus help us to handle life joyfully, even though it doesn’t change our circumstances. |
|||
06 Jul 2009, 17:37 |
|
windwakr 06 Jul 2009, 17:58
Just look at all asmcoders posts, he posts like hes a dumb two year old and he has absolutely no searching skills.
But anyway, Bicyclist, edit your post and put the code tags around the code, they turn something like org 100h push 0a000h pop es mov ax,13h int 10h into Code: org 100h push 0a000h pop es mov ax,13h int 10h Much easier on the eyes. Or, Loco if you are reading this, could you edit the code tags into his post. Thanks |
|||
06 Jul 2009, 17:58 |
|
pal 06 Jul 2009, 18:05
Bicyclist: use OllyDbg to step through the code until you get the line which doesn't execute.
windwakr: lol. |
|||
06 Jul 2009, 18:05 |
|
LocoDelAssembly 06 Jul 2009, 18:08
windwakr, I have added the code tags.
Bicyclist, you are running the same executable that works in 32-bit or you are recompiling for 64-bit? |
|||
06 Jul 2009, 18:08 |
|
Bicyclist 06 Jul 2009, 18:46
LocoDelAssembly wrote: windwakr, I have added the code tags. Yes, I recompiled for 64 bit. |
|||
06 Jul 2009, 18:46 |
|
Bicyclist 06 Jul 2009, 18:50
pal wrote: Bicyclist: use OllyDbg to step through the code until you get the line which doesn't execute. Thanks. I will do that and see where it stops at. |
|||
06 Jul 2009, 18:50 |
|
Bicyclist 06 Jul 2009, 19:09
pal wrote: Bicyclist: use OllyDbg to step through the code until you get the line which doesn't execute. Ollydbg would not work, so I used MS's debugger. This is what it said. Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. CommandLine: C:\masm32\Source\Firework3.exe Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ModLoad: 00000000`00400000 00000000`00404000 image00000000`00400000 ModLoad: 00000000`776d0000 00000000`77850000 ntdll.dll ModLoad: 00000000`77870000 00000000`779d0000 ntdll32.dll ModLoad: 00000000`759b0000 00000000`759f5000 C:\Windows\system32\wow64.dll ModLoad: 00000000`75880000 00000000`758ce000 C:\Windows\system32\wow64win.dll ModLoad: 00000000`759a0000 00000000`759a9000 C:\Windows\system32\wow64cpu.dll (310.da4): Break instruction exception - code 80000003 (first chance) *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll - ntdll!DbgBreakPoint: 00000000`77714ea0 cc int 3 0:000> g ModLoad: 00000000`775a0000 00000000`776cc000 WOW64_IMAGE_SECTION ModLoad: 00000000`76740000 00000000`76850000 WOW64_IMAGE_SECTION ModLoad: 00000000`775a0000 00000000`776cc000 NOT_AN_IMAGE ModLoad: 00000000`774d0000 00000000`7759d000 NOT_AN_IMAGE ModLoad: 00000000`76740000 00000000`76850000 C:\Windows\syswow64\kernel32.dll ModLoad: 00000000`75df0000 00000000`75e80000 C:\Windows\syswow64\gdi32.dll ModLoad: 00000000`76370000 00000000`76440000 C:\Windows\syswow64\USER32.dll ModLoad: 00000000`75ae0000 00000000`75ba6000 C:\Windows\syswow64\ADVAPI32.dll ModLoad: 00000000`76200000 00000000`762f0000 C:\Windows\syswow64\RPCRT4.dll ModLoad: 00000000`75a20000 00000000`75a80000 C:\Windows\syswow64\Secur32.dll (310.da4): WOW64 breakpoint - code 4000001f (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll32.dll - ntdll32!DbgBreakPoint: 77880004 cc int 3 |
|||
06 Jul 2009, 19:09 |
|
LocoDelAssembly 06 Jul 2009, 19:20
Quote:
Don't do that then. You are not using 64-bit pointers which probably are making all the mess. From the debug output you show looks like the code is 32-bit actually but if it is not then you must either recompile for 32-bit (or use the same executable you use under WinXP 32-bit) or do a major rewrite of your code to support 64-bit properly. |
|||
06 Jul 2009, 19:20 |
|
Bicyclist 06 Jul 2009, 19:52
LocoDelAssembly wrote:
I meant to say that I recompiled it on a 64 bit machine using a 32 bit compiler and linker. I get the same message as when I ran the original executable. Vista claims that it can run 32-bit apps. It may be because this code does not use the Window APIs. Microsoft likes to lessen our choices and decide what is best. I will stick with XP Pro on my home computer. Take care. |
|||
06 Jul 2009, 19:52 |
|
Madis731 06 Jul 2009, 21:48
Maybe you can post us the executable for the ones without MASM-skills
Then those of use (me, bitRake & others) can test and post the results. It can be many things: unaligned stack, unaligned SSE memory-access etc. Don't know which it is - http://fdbg.x86asm.net/ - maybe helps... |
|||
06 Jul 2009, 21:48 |
|
Bicyclist 06 Jul 2009, 21:53
Madis731 wrote: Maybe you can post us the executable for the ones without MASM-skills Thanks. I have attached it as a zip file.
|
|||||||||||
06 Jul 2009, 21:53 |
|
LocoDelAssembly 06 Jul 2009, 22:14
I have experienced problems with OllyDbg under WinXP x64, but as far as I can recall, the only thing needed was just to forward the firsts exceptions to the program. I haven't tested OllyDbg 2 there though, perhaps it works better? Give it a try: http://www.ollydbg.de/odbg200j.zip
PS: I've used OllyDbg under 64-bit but debugging 32-bit apps, otherwise it really has no chances to work |
|||
06 Jul 2009, 22:14 |
|
bitRAKE 06 Jul 2009, 22:26
Works fine in WinXP 64-bit (unless I change the window size). I'm familiar with this program. First thought is possible Heap size too small. Then check threading for possible conflict. I like his spiral program, too! Modern processors run these programs WAY too fast, imho.
(Looks like there is a new version than you are using as well? Or you changed it?) Last edited by bitRAKE on 06 Jul 2009, 23:01; edited 2 times in total |
|||
06 Jul 2009, 22:26 |
|
Bicyclist 06 Jul 2009, 22:30
LocoDelAssembly wrote: I have experienced problems with OllyDbg under WinXP x64, but as far as I can recall, the only thing needed was just to forward the firsts exceptions to the program. I haven't tested OllyDbg 2 there though, perhaps it works better? Give it a try: http://www.ollydbg.de/odbg200j.zip OllyDbg 2.0 does load it. I ran Debug and Run. Is there some info you need from one of the panes? It has been a while since I used Ollydbg. I would like to go one instruction at a time but can't figure out how to do that. Outta here. |
|||
06 Jul 2009, 22:30 |
|
bitRAKE 06 Jul 2009, 22:36
F7 to step
F8 to step over F9 to run |
|||
06 Jul 2009, 22:36 |
|
Bicyclist 07 Jul 2009, 01:47
I think I found the problem.
The debugger gave this message. ERROR_DEFECTIVE_OPERATING_SYSTEM |
|||
07 Jul 2009, 01:47 |
|
Goto page 1, 2 Next < Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.