Index
> Compiler Internals > I have found not critical bug |
| Author |
|
|
EvilsInterrupt 30 Nov 2006, 21:50
Code: str_ReadFile db 'ReadFile',0x0 str_WriteFile db 'WriteFile',0x str_CloseHandle db 'CloseHandle',0x0 second string is bad, but fasm it assembled success! is it not right!
_________________ In code Veritas! (lat.) Last edited by EvilsInterrupt on 01 Dec 2006, 04:16; edited 2 times in total |
|||||||||||
30 Nov 2006, 21:50 |
|
(and a very old one, FASMW 1.64 has the same behavior)[/edit]|
EvilsInterrupt 01 Dec 2006, 04:24
Quote: Your uploaded code does not contain the posted code Sorry, file updated. Code: api_CloseHandle dd 0 db 0x  |
|||
|
01 Dec 2006, 04:24 |
|
|
LocoDelAssembly 01 Dec 2006, 13:33
Well, it's not a bug
 . I'm trying to upload an image to imageshack but my internet connection has serious routing problems and I can just reach few sites (like this). I'll upload it as soon as posible but in advance I can tell that things like "a = 0x+5" and "return 0x" is accepted by Turbo C 2.0
[edit] 
Before: Code: Traza a la dirección imageshack.us [38.99.76.137] sobre un máximo de 30 saltos: 1 * * * Tiempo de espera agotado para esta solicitud. 2 18 ms 19 ms 19 ms 200.51.241.249 3 18 ms 19 ms 20 ms 200.51.233.142 4 10 ms 19 ms 19 ms 200.51.233.135 5 * * * Tiempo de espera agotado para esta solicitud. 6 * * * Tiempo de espera agotado para esta solicitud. . . . Now  : Code: Traza a la dirección imageshack.us [38.99.76.137] sobre un máximo de 30 saltos: 1 * * * Tiempo de espera agotado para esta solicitud. 2 12 ms 10 ms 11 ms 200.51.241.249 3 11 ms 10 ms 11 ms 200.51.233.142 4 10 ms 10 ms 11 ms 200.51.233.135 5 73 ms 69 ms 11 ms 213.140.36.218 6 137 ms 69 ms 68 ms 213.140.43.69 . . . [/edit] |
|||
|
01 Dec 2006, 13:33 |
|
|
EvilsInterrupt 01 Dec 2006, 14:45
Ok, I`m understand.
Sorry my english is bad! But I`m stady it is language now |
|||
|
01 Dec 2006, 14:45 |
|
|
optimizator 15 Dec 2006, 19:23
I don't want to make a new thread - I find another bug. When I'm using global variables (FASMINC defined into "My Computer") this code cause error:
Code: format PE GUI 4.0 entry start include '%FASMINC%\win32a.inc' ... section '.code' code executable start: ... When line entry start is absent there, compilation success! Next code fragment was compiled normally: Code: format PE GUI 4.0 include '%FASMINC%\win32a.inc' ... section '.code' code executable start: ... .end start |
|||
|
15 Dec 2006, 19:23 |
|
|
Tomasz Grysztar 15 Dec 2006, 19:32
I'm not able to reproduce this problem, can you post more complete information?
|
|||
|
15 Dec 2006, 19:32 |
|
|
kohlrak 15 Dec 2006, 21:04
Quote: format PE GUI 4.0 Did you include a "ret" or "ExitProcess, 0  |
|||
|
15 Dec 2006, 21:04 |
|
|
optimizator 16 Dec 2006, 07:44
Excuse, but I think it not an error of the compiler. When I have added section of import - the program has earned:
Code: format PE GUI 4.0 entry start include '%FASMINC%\WIN32AXP.INC' section '.code' code readable executable start: invoke ExitProcess,1 section '.idata' import readable library kernel,'KERNEL32.DLL' import kernel,ExitProcess,'ExitProcess' But why the following code works without creation of section of import? Code: format PE GUI 4.0 include '%FASMINC%\WIN32AXP.INC' section '.code' code readable executable start: invoke ExitProcess,1 .end start And the last question: how I can disable generation by the compiler of a prologue and an epilogue of function? For example in MASM it is done so: Code: option prologue:none option epilogue:none |
|||
|
16 Dec 2006, 07:44 |
|
|
Tomasz Grysztar 16 Dec 2006, 08:23
Answer for the first question comes from Win32 headers documentation, section 2.2:
Quote: The extended headers enable some macroinstructions that help with easy structuring the program. The .data and .code are just the shortcuts to the declarations of sections for data and for the code. The .end macroinstruction should be put at the end of program, with one parameter specifying the entry point of program, and it also automatically generates the import section using all the standard import tables. For the second problem: you may even do it exactly as in MASM, if you include MACRO/MASM.INC file, which defines "option" macro. |
|||
|
16 Dec 2006, 08:23 |
|
< Last Thread | Next Thread > |
Forum Rules:
|