wtf: wtf: cabi/mem-cabi.cc:34: static bool BX_MEM_C::dbg_fetch_mem(BX_CPU_C, bx_phy_address, unsigned int, Bit8u): Assertion `false' failed.

Hi, just giving it a shot at fuzzing with Windows. I have generated my corpus and states, but upon running them on windows it’s throwing the assertion error. not sure what I am doing wrong here.

Command

### Server
./wtf master --name sspisrv  --max_len 1024 --runs=50000 --target /mnt/c/Users/Kiwi/Desktop/wtf/targets/

### Node
sudo ./wtf fuzz --name sspisrv --limit 500000 --target /mnt/c/Users/Kiwi/Desktop/wtf/targets

### On Linux Error
Setting @fptw to 0xff'ff.
The debugger instance is loaded with 5 items
Setting debug register status to zero.
Setting debug register status to zero.
Could not set a breakpoint at hal!HalpPerfInterrupt.
Failed to set breakpoint on HalpPerfInterrupt, but ignoring..
Dialing to tcp://localhost:31337/..
wtf: cabi/mem-cabi.cc:34: static bool BX_MEM_C::dbg_fetch_mem(BX_CPU_C*, bx_phy_address, unsigned int, Bit8u*): Assertion `false' failed.
Aborted
### On Windows Error
Setting @fptw to 0xff'ff.
Initializing the debugger instance.. (this takes a bit of time)
Setting debug register status to zero.
Setting debug register status to zero.
Could not set a breakpoint at hal!HalpPerfInterrupt.
Failed to set breakpoint on HalpPerfInterrupt, but ignoring..
Dialing to tcp://localhost:31337/..
Assertion failed: false, file cabi/mem-cabi.cc, line 34

Any pointer will be helpful!! Thanks!

About this issue

Original URL
State: closed
Created 10 months ago
Comments: 18 (5 by maintainers)

Most upvoted comments

Circling back on this; @kiwids0220 is there something else we can help you with or are we good to close?

Cheers

I moved onto something else and yes we can close this one now

kiwids0220 on Sep 30, 2023

Circling back on this; @kiwids0220 is there something else we can help you with or are we good to close?

Cheers

0vercl0k on Sep 30, 2023

For sure, Here is the screenshot for the errors I was getting! Another interesting behavior I noticed is that when running KVM backend, the fuzz fails with KVM backend initialization, and when running with bochscpu backend, the fuzzer will initialize successfully but fails over a dozen of cases (Shown in the Windows error screenshot below)

On WSL Ubuntu running kvm backend

On Windows 11 running bochscpu backend

kiwids0220 on Sep 3, 2023

Hello 👋🏽

Pretty interesting one, I don’t think I have ever seen this; it seems that you are hitting this assert:

bool BX_MEM_C::dbg_fetch_mem(BX_CPU_C *cpu, bx_phy_address addr, unsigned len, Bit8u *buf)
{
    assert(false);

    return false;
}

I have got no clue why though - I’ll investigate what’s going on; thank you for reporting.