Dump window -> Format Unsigned long long (64 bit) -> scroll little bit -> x64dbg crashes with memory access violation. Known?

Another critical issue:

 

 

1. Double click on mov r8, API_addr

2. Don't change anything, click OK.

3. Code became corrupted:

 

Edited June 2, 201411 yr by fetch

Just playing with x32 a little.

 

Is there a known bug where it just ends the disassembly? Not sure if its crashing the disassembler as it stops during some data bytes which I guess it might have issues with if it is trying to disassemble to code?

 

@fetch: I cannot reproduce the crash on my system (the unsigned long long one), the other problem you are reporting is an assembler problem, the assembler is not part of x64_dbg, it's a standalone project that I currently do not support. Sorry about that. The actual issue is that rip-relative addressing is not supported so it will try to create a direct reference.

@Loki: this is not actually a problem, the end of the memory page is just reached. For example you have

.text, addr 401000, size 3000, protection ReadWriteExecute

now you do:

VirtualProtect(402000, 2000, ReadExecute)

it will become:

.text addr 401000, size 1000, protection ReadWriteExecute.text addr 402000, size 2000, protection ReadExecute

x64_dbg will see this as two different pages (currently) so the disassembly ends.

Greetings,

Mr. eXoDia

PS I go to Paris now (yay), so I might not respond to anyone for some time.

I should have noticed it was the end of the page

 

No plans to either add next page or give a 'show more' type view? Just helps when doing a little static analysis

 

Have fun in Paris!

 

PS I go to Paris now (yay), so I might not respond to anyone for some time.

 

 

So Armadillo developers and others can stay cool now knowing that you are away...

PS I go to Paris now (yay), so I might not respond to anyone for some time.

have a good time, for the moment everything works here with x64dbg!