HARI MAHADEVAN (何瑞理)

If you search the web using the title of this post, you'll get many links to articles most of which explain how to set this up using a virtual COM port on the VM. Coming from driver background that goes back over 20 years, at first this seemed quite natural. But then I remembered that using WinDBG over COM port to be painfully slow. And recent adventures in OSX land using LLDB led me to wonder if WinDBG over network would to be possible? Well it turns out that WinDBG over Ethernet is indeed possible and is documented by Microsoft here . However, they miss out on certain key steps, which won't be obvious for the casual reader unless one reads the entire driver debugging documentation from the beginning. This post captures all the requisite steps as a quick reference guide. I used one of the freely available MSEdge on Windows 10 VM for   VirtualBox . It's only valid for 90 days, but 90 days was more than enough for my little excursion into the driver land. If you want a...

A recent project requirement from a customer for a cross-platform solution prompted me to look into viable frameworks for this. Based on my knowledge of languages (C++, Python & Javascript), I narrowed the potential solutions to wxWidgets & Git Electron. Since I have been spending some time with Python over the last two years and given its ease of use, I through I'll look into wxPython, the Python projection of wxWidgets framework. Here are my notes from this research today morning: wxPython provides a genuine means to build cross platform GUI apps (installed through PyPi pip install wxpython ). Python code can be compiled into distributable binaries using cx_Freeze , another cross-platform tool that can generate binaries for Windows, Mac & Linux. cx_Freeze can provide executable files as well as installable binaries such as MSI or DMG files. cx_Freeze source repo has sample code for various deployment scenarios. One of them is wxPython based application. Py2Ex...

Running celery on Windows, shows the following error when tasks are queued to be executed: ValueError: not enough values to unpack (expected 3, got 0) The way to fix this is to add --pool=solo to the celery daemon command line. This makes celery run as a solo process and without concurrency, which for development purposes shouldn't be a big deal. So the entire daemon command would look something like this: python -m celery -A config worker --pool=solo -l info Taken from this Github thread .