Index
> Projects and Ideas > a hex viewer in FASMGoto page Previous 1, 2 |
| Author |
|
|
Flier-Mate 30 Jul 2023, 15:50
int0x50 wrote: there is some bug in the argument processing code ... but the error you have given, usually happens if you run the fih.exe through batch file ... I think I understand that, my Win32 command-line programs are the opposite, can run in CMD but cannot parse the filename correctly in PowerShell. 
int0x50 wrote:
It is "print_newline".... maybe you didn't update the fih.asm. Nice work, by the way. |
|||
30 Jul 2023, 15:50 |
|
|
int0x50 31 Jul 2023, 02:39
printn is a function defined within libs.inc as :
proc printn, inputstring just below print_newline: ... it's like printf, "hey" vs printf, "hey", 13, 10 ... need to remove these redundant codes .. code cleanup is something i am planning today along with bug fixes ... |
|||
|
31 Jul 2023, 02:39 |
|
|
int0x50 31 Jul 2023, 03:23
ran the same tests (assembly vs powershell)
input file size: 105 MB - 110596096 bytes.
|
|||||||||||||||||||
|
31 Jul 2023, 03:23 |
|
||||||||||||||||||
|
int0x50 31 Jul 2023, 09:35
when I run fih.exe sample.exe, as a command it runs fine ..
but when I give that command in a bat file, somehow the last 'e' gets skipped ... how do I debug this scenario? JIT (with int3) is not working ... point is, i need to run my fih.exe through batch command, and make it break at interesting locations on x64dbg ... |
|||
|
31 Jul 2023, 09:35 |
|
| Goto page Previous 1, 2 < Last Thread | Next Thread > |
Forum Rules:
|