Is there a source level disassembler that works with PureBasic?
I would like to examine the actual x86 or x64 generated code that corresponds to the original PB source.
Source Level Disassembler for PureBasic?
Source Level Disassembler for PureBasic?
Think Unicode!
Re: Source Level Disassembler for PureBasic?
Actualy PB generates asm code. You can keep the commented (comments are the PB source lines) asm file by launching the PB compiler with the parameter /COMMENTED.ElementE wrote:Is there a source level disassembler that works with PureBasic?
I would like to examine the actual x86 or x64 generated code that corresponds to the original PB source.
Re: Source Level Disassembler for PureBasic?
Thanks Thorium.Actualy PB generates asm code. You can keep the commented (comments are the PB source lines) asm file by launching the PB compiler with the parameter /COMMENTED.
PureBasic seems to have already built into it everything that a programmer needs.
Think Unicode!
Re: jas
I use OllyDbg or x64dbg to debug assembly code.jas wrote:For assembly programming a better debugger or a way to send debug info to another debugger would be nice.
Just put a "!int 3" befor your code, to trigger a breakpoint in the debugger. Then i single step through the code.
Re: Source Level Disassembler for PureBasic?
You can use Bochs (x86 emulator), i love it !
You'll also debug the OSWhen you're using Bochs with the internal debugger, you can trigger the debugger via a facility called magic breakpoints. To trigger a breakpoint, you can insert xchg bx, bx (in GAS syntax, xchgw %bx, %bx) anywhere in the code and Bochs will trap into the debugger as soon as it executes it. On real hardware this has no effect as it merely replaces the BX register with itself.
You should put the following line in your Bochs configuration file to have it listen to magic breakpoints: magic_break: enabled=1
jas
Thorium wrote:I use OllyDbg or x64dbg to debug assembly code.jas wrote:For assembly programming a better debugger or a way to send debug info to another debugger would be nice.
Just put a "!int 3" befor your code, to trigger a breakpoint in the debugger. Then i single step through the code.
Exactly my point. Having to halt a program then use another debugger is required to see the actual disassembly and the full register set. It reminds me of how I had to program personal computers back in the 1980s before source-level assembly debuggers.