Comments (4)
Hi hex64dbg,
To troubleshot the issue you can enable JSON log in rsconfig.py (IDA retstync plugin)
ret-sync/ext_ida/retsync/rsconfig.py
Line 110 in ac41c81
To this:
# enable/disable logging JSON received in the IDA output window
DEBUG_JSON = True
# global log level (console output)
LOG_LEVEL = logging.DEBUG
Also you can enable extra debugging for dispatcher and broker in the rsconfig.py
file:
# enable/disable broker and dipatcher exception logging to file
LOG_TO_FILE_ENABLE = True
It will generate a log file in your %tmp%
folder if an exception is triggered (like retsync.dispatcher.py.err
)
Just as a guess, it seems dispatcher encounters an issue and crash without warning its broker(s). Hopefully log file will tell us more.
from ret-sync.
Thanks a lot for the help.
I followed you instructions. Here is the IDA ouptut
[sync] plugin loaded
[sync] parse_exec -> [sync]{"type":"broker","subtype":"msg","msg":"connected to dispatcher"}
[sync] << broker << connected to dispatcher
[sync] parse_exec -> [sync]{"type":"broker","subtype":"notice","port":"52989"}
[sync] << broker << listening on port 52989
Then in WinDbg
0: kd> .load sync
[sync] DebugExtensionInitialize, ExtensionApis loaded
0: kd> !sync
[sync] No argument found, using default host (127.0.0.1:9100)
[sync] sync success, sock 0x344
[sync] probing sync
[sync] sync is now enabled with host 127.0.0.1
[sync] recv: connection closed
[sync] sync is off
And there is still no output in IDA. A log file was generated in the %tmp% folder "retsync.broker.py.err", but it's empty.
So I think the issue is on the WinDbg side. The WinDbg extension was compiled with VS2019, x64 configuration. Maybe you could provide pre-built binaries, like for the other extensions ?
I also tried Ghidra and there is also an issue, this confirms the problem lies with WinDbg. Can I enable verbose extension debugging in WinDbg like in IDA ?
Here is the Ghidra output
*] retsync init
[>] programOpened: ntoskrnl.exe
imageBase: 0x140000000
[>] xxxxxxx programActivated: ntoskrnl.exe
local addr: 140000000, remote: unknown
The plugin windows always shows "status: idle", even after I !sync
from WinDbg
Thanks for your time.
from ret-sync.
So I think the issue is on the WinDbg side. The WinDbg extension was compiled with VS2019, x64 configuration. Maybe you could provide pre-built binaries, like for the other extensions ?
Regarding this point, I don't get it, Windbg extensions are provided as well on the pipeline, see:
update: The UI has changed a little, under "related" tab, one should click on 6 published. Not very intuitive. Sorry for that
From:
[sync] plugin loaded
[sync] parse_exec -> [sync]{"type":"broker","subtype":"msg","msg":"connected to dispatcher"}
[sync] << broker << connected to dispatcher
[sync] parse_exec -> [sync]{"type":"broker","subtype":"notice","port":"52989"}
[sync] << broker << listening on port 52989
It seems the dispatcher is definitely implied here, you should receive more message from him.
What you experience here, reminds me of the symptoms from :
#32
Would it be possible that the port 9100 (or another one if you've redefined it), is already used? Possibly by a zombie Python process ? There may be a common issue that I don't fully get so far.
from ret-sync.
Regarding this point, I don't get it, Windbg extensions are provided as well on the pipeline, see:
Sorry I missed that, but it didn't solve the issue.
Would it be possible that the port 9100 (or another one if you've redefined it), is already used?
Exactly ! That process is Logitech G HUB and it uses the same port indeed.
Everything is settled, thank you for the support.
from ret-sync.
Related Issues (20)
- EXT_BN few observations
- X64DBG Install Guide Needs Update HOT 1
- x64dbg and Ghidra 10.2 [x] translate failed, syncing not enabled [x] program unavailable: ntdll.dll HOT 4
- can't use on IDA7.7 HOT 4
- About idb is disabled new problem (I have solved it myself)
- Building ret-sync for Ghidra 10.3.1 HOT 7
- [New Feature] support visual studio
- extension not triggering from ghidra 10.4 codebrowser. HOT 2
- program unavailable
- "sync" category for binary ninja
- plugin not working for IDA 8.3 HOT 1
- Integrating Registers and Stack Display in IDA with LLDB Synchronization
- There was a problem connecting WinDbg to IDA
- IDA+windbg: mod request has no match for ntkrnlmp.exe HOT 1
- asyncore is gone in python3.12
- Are some commands like `jmpto` not available for x64dbg?
- Mismatch of instruction from IDA and GDB
- This repository seems to be dead... Active one at https://github.com/diommsantos/Gx64Sync
- Can't install plugin in IDA 7.5 HOT 1
- Bug in IDA plugin
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ret-sync.