<Niklas> Nevermind found it
bridgemain.h 964:BRIDGE_IMPEXP int DbgGetBpList(BPXTYPE type, BPMAP* list);
<SunBeam> is there a limit to how many characters a script line accepts?
<SunBeam> line 10112, as you can see in the text file, has no issues
<SunBeam> line 10112 is split in the script window in 2 lines 😄
<SunBeam> I'm executing a simple script that applies labels to addresses
<SunBeam> this is line 10112
<SunBeam>
lbl 143CB8478,"const hkSignal2<hknpEventHandlerInput const &,hknpEvent const &>::MemberSlot<Physics::ighkTheGenericSingletonContactListener,void (Physics::ighkTheGenericSingletonContactListener::*)(hknpEventHandlerInput const &,hknpEvent const &)>::vftable'"`
<SunBeam> yeaps, I think the script tab accepts
240 characters for a line 🙂 (re @SunBeam: lbl 143CB8478,"const hkSignal2<hknpEventHandlerInput const &,hknpEvent const &>::MemberSlot<Physics::ighkTheGenericSingletonContactListener,void (Physics::ighkTheGenericSingletonContactListener::*)(hknpEventHandlerInput const &,hknpEvent const &)>::vftable'"`)
<Federico> Tried DbgGetModuleAt(info->cip, name);
<Federico> and fails
<Federico> Also tried:
<Federico> Module::ModuleInfo mi;
<Federico> Module::InfoFromAddr(info->cip, &mi);
<Federico> and fails as well
<Federico> any clues?
<Federico> info->cip is the the current RIP pointer to a valid code address within the module being debugged
Hello. I might be wrong but, looking at DbgGetModuleAt my first idea is that name should be atleast MAX_MODULE_SIZE long.
<Federico> Is there any GetLastError() function
<Federico> ?
<Federico> works with other exes. Could this be true?
Im setting a variable in a bp like cmd($myVariable={rax})
Is it possible to use this variable in a different bp as a pointer to a string and log that string like log(s:{$myVariable})?
Or storing a string in the variable like cmd($myVariable={s:rax}) is ok too.
I feel like i just cant get the expression right.
Is it possible to use this variable in a different bp as a pointer to a string and log that string like log(s:{$myVariable})?
Or storing a string in the variable like cmd($myVariable={s:rax}) is ok too.
I feel like i just cant get the expression right.
<mrexodia> $myVariable={rax} isn’t a valid command (re @x64dbg_bot: <feketeimre> Im setting a variable in a bp like cmd($myVariable={rax})
Is it possible to use this variable in a different bp as a pointer to a string and log that string like log(s:{$myVariable})?
Or storing a string in the variable like cmd($myVariable={s:rax}) is ok too.
I feel like i just cant get the expression right.)
Is it possible to use this variable in a different bp as a pointer to a string and log that string like log(s:{$myVariable})?
Or storing a string in the variable like cmd($myVariable={s:rax}) is ok too.
I feel like i just cant get the expression right.)
<mrexodia> You can do myVariable=rax
<mrexodia> And then in the logging use {s:myVariable}
<mrexodia> Or {utf8@myVariable}
Thank you.
<MrDbg> Friends
<MrDbg> So is this where I ask questions about x64dbg ?
<mrfearless> check out the blog: https://x64dbg.com/blog/ (re @MrDbg: Is there a tips documentation on x64dbg)
<mrfearless> also search for "some x64dbg usage" in this channel to view some posts related to x64dbg usage like in malware research that have been posted on twitter
<mrfearless> or for documentation about x64dbg, check out https://help.x64dbg.com/en/latest/
<Magnius> http://linux.x64dbg.com/