Index
> Compiler Internals > fasm.exe crash on setting include variable |
| Author |
|
|
madmatt 02 Mar 2015, 22:01
I get a crash when I try and set the 'INCLUDE' variable to a value with fasm.exe. below is the crash dump info:
_________________ Gimme a sledge hammer! I'LL FIX IT! |
|||||||||||
02 Mar 2015, 22:01 |
|
|
revolution 02 Mar 2015, 23:57
Can you please give the steps needed to reproduce the crash.
|
|||
|
02 Mar 2015, 23:57 |
|
|
revolution 03 Mar 2015, 00:17
l_inc: Thanks. That is much more concise the a crash dump.
|
|||
|
03 Mar 2015, 00:17 |
|
|
madmatt 03 Mar 2015, 12:42
Sorry about that, here's some more info:
I set up the %PATH% variable to my fasm directory and include: c:\fasmw64\ ; c:\fasmw64\w7include64\ but that still wouldn't compile my 64bit example. So I tried to set the include directory with fasm, which then caused the crash: C:\FASMW64\W7Examples64\Misc>fasm customfonta.asm -d INCLUDE=c:\fasmw64\w7include64 flat assembler version 1.71.36 (1048576 kilobytes memory) |
|||
|
03 Mar 2015, 12:42 |
|
|
revolution 03 Mar 2015, 13:06
fasm doesn't read the PATH variable. It reads the INCLUDE variable.
But the problem is as l_inc described, setting a reserved preprocessor keyword using the d switch. In your case the reserved word is INCLUDE. |
|||
|
03 Mar 2015, 13:06 |
|
|
Tomasz Grysztar 03 Mar 2015, 15:05
Fixed in 1.71.37.
|
|||
|
03 Mar 2015, 15:05 |
|
|
madmatt 03 Mar 2015, 16:24
I see now, that is how NOT to set the 'INCLUDE' variable
 |
|||
|
03 Mar 2015, 16:24 |
|
|
l_inc 08 Mar 2015, 12:54
I see there was a silent improvement update on this today, but the Windows package now contains a compiled DOS executable instead of a console PE.
_________________ Faith is a superposition of knowledge and fallacy |
|||
|
08 Mar 2015, 12:54 |
|
|
revolution 08 Mar 2015, 13:08
Heh, I tried it on a win7 box:
Quote: --------------------------- Notice the misspelling of "incompatibity". |
|||
|
08 Mar 2015, 13:08 |
|
|
Tomasz Grysztar 08 Mar 2015, 14:00
I apologize, I had some small local problems and while I tried to correct the packages I actually made them worse. And it seems another overzealous AV started to delete some of my executable files as soon as I compiled them (I used to just laugh whenever this happens), thus disrupting my build process.
|
|||
|
08 Mar 2015, 14:00 |
|
|
l_inc 08 Mar 2015, 14:21
Tomasz Grysztar
Quote: it seems another overzealous AV started to delete some of my executable files I gave up on AV 5-6 years ago. Lots of issues such as system slowdown and destabilization as well as false positives, but failing to protect against real threats. Thus I sticked to a pure proactive defense as a firewall module with lots of close-to-paranoid manual on-demand configuration (comodo firewall or agnitum outpost firewall would go). _________________ Faith is a superposition of knowledge and fallacy |
|||
|
08 Mar 2015, 14:21 |
|
< Last Thread | Next Thread > |
Forum Rules:
|