I am debugging an ARM64 process written in Rust on Mac M1 , ussng vscode-lldb extension in VSCode.
I can see panels including Variables/Breakpoints/Modules. But the Callstack panel is missing. I want to look for the function calling the current function. Please how to find the Callstack panel in VSCode-lldb extention? Currrently I have to execute thread backtrace in debugging console to view the frames
Related
I'm trying to set a breakpoint on CLSIDFromProgID while debugging Excel (32 bit) as I'm looking into an add-in issue. So far I haven't figured out how to do it on Win10. Both the Visual Studio (17) debugger and WinDbg say they have loaded the symbols for ole32.dll. I've tried:
in WinDbg:
ole32!CLSIDFromProgID
ole32!_CLSIDFromProgID
ole32!_CLSIDFromProgID#8
CLSIDFromProgID
_CLSIDFromProgID
_CLSIDFromProgID#8
in visual studio:
{,,ole32.dll}CLSIDFromProgID
{,,ole32.dll}_CLSIDFromProgID
{,,ole32.dll}_CLSIDFromProgID#8
CLSIDFromProgID
_CLSIDFromProgID
_CLSIDFromProgID#8
In some cases it seemed to set a breakpoint but it was actually in some other module so that didn't help. If I view the exported CLSIDFromProgID in ole32.dll on Win10 I see:
CLSIDFromProgID (forwarded to api-ms-win-core-com-l1-1-0.CLSIDFromProgID)
When I use the DBH tool included with WinDbg to list the symbols in ole32.pdb, the only CLSIDFromProgID symbol I see is:
_imp__CLSIDFromProgID
while debugging Excel and having already executed the code which calls CLSIDFromProgID I don't see module api-ms-win-core-com-l1-1-0.dll loaded.
Anyone successful putting a breakpoint of any of these forwarded API's?
[Edit]
By the way, if you want Excel to call CLSIDFromProgID you can enter the following in a cell:
=RTD("MyBogus.ProgId", "", "Foo")
Thanks,
Nick
I recently installed Selenium on my Mac. After the install I am unable to get my existing tkinter code to work properly. I don't know if the problem occurred when I installed Selenium or when I installed the Firefox drivers. Prior to the install (I use Pycharm) when I ran the python code that creates my GUI there were no problems but after the install the python code that creates the GUI doesn't work at all, more specifically nothing happens and no GUI is initialized. No error message is given but the tkinter GUI I built doesn't initialize. If I exit Pycharm and try running the code that initializes my GUI from IDLE then all the background code runs but the GUI itself does not appear. Running the GUI code from IDLE does cause the following error message to be displayed:
objc[1222]: Class TKApplication is implemented in both /System/Library/Frameworks/Tk.framework/Versions/8.5/Tk (0x108da81f8) and /Users/BioASys/anaconda/lib/libtk8.5.dylib (0x115b26e40). One of the two will be used. Which one is undefined.
Apparently the Selenium install caused the TKApplication class to be implemented in two different locations and this conflict is causing tkinter to not initialize properly. I've worked through all of the Q&A's I could find on this topic but nothing seems to work. If anybody has any ideas on how I can fix this I would appreciate the help.
I'm using Haxe to build a windows executable. When running the exec, error messages are really brief (eg: "Error: Null function") with no line numbers or stack traces.
I'm compiling the executable using the -debug flag (which is, in theory, supposed to enable a stacktrace on error) with no luck.
I looked into this page ( http://haxe.org/doc/cross/exceptions ) and was hoping to override the default error-handling function, but there's no instructions on how to do that for a windows exec; only for flash/js/neko.
If I throw the game into a try/catch, I can manually grab the errors and call my own getTrace() and I'm happy, but it's gotten to the point where I'm not sure where to place my try/catch calls and really need to get this working.
Any tips?
Hi I am using NVidia Nsight 2.2, have a GTS 450 card and latest drivers. Windows Vista 64 bit. When launching graphics debugger the application crashes on the very 1st drawcall. The callstack looks like this:
nvwgf2um.dll!5bdd7d53()
[Frames below may be incorrect and/or missing, no symbols loaded for nvwgf2um.dll]
nvwgf2um.dll!5be9c7f7()
nvwgf2um.dll!5bde377e()
nvwgf2um.dll!5bc02afb()
nvwgf2um.dll!5bc0257b()
nvwgf2um.dll!5bc0259e()
nvwgf2um.dll!5bdd0612()
nvwgf2um.dll!5bcb2292()
nvwgf2um.dll!5bc45072()
nvwgf2um.dll!5bcbff8c()
D3D11SDKLayers.dll!5ea52f2f()
Nvda.Graphics.Interception.100.dll!5dbb2853()
Nvda.Graphics.Interception.100.dll!5dba317e()
Nvda.Graphics.Interception.100.dll!5db99b21()
Nvda.Graphics.Interception.100.dll!5df0150f()
Otherwise it runs fine by itself, only crashes if I launch through Nsight graphics debugger.
I suspect this is somehow related to me using DX11 dynamic shader linkage. Since my other applications that don't use dynamic linkage run fine. Anybody experienced this before, or has any info on this issue with Nsight?
What driver and exact build of 2.2 are you using? (Nsight->Help->About Nsight->Build number)
The problem might be related to DX Control Panel's debug layer setting. (Please check my comments in Sebastien's answer).
I am using remote (k)gdb to debug a problem in a module that causes a panic when loaded e.g. when init() is called.
The stack trace just shows that do_one_initcall(mod->init) causes the crash. In order to get the symbol file loaded in the gdb, I need to get the address of the module text section, and to get that I need to get the module loaded.
Because the insmod in busybox (1.16.1) doesn't support -m so I'm stuck to grep modulename /proc/modules + adding the offset from nm to figure out the address.
So I'm facing a sort a of a chicken and an egg problem here - to be able to debug the module loading, I need to get the module loaded - but in order to get the module loaded, I need to debug the problem...
So I am currently thinking about two options - is there a way to get the address information either:
by printk() in the module init code
by printk() somewhere in the kernel code
all this prior to calling the mod->init() - so I could place a breakpoint there, load the symbol file, hit c and see it crash and burn...
Can you build your code into the kernel rather than as a module? That might simplify debugging the init() call.
You could also set a breakpoint at do_one_initcall() and look at the address of mod->init to get the load address.