Posts

Showing posts with the label debugging

Breakpoints not being hit in JetBrains Rider?

Image
Clash Royale CLAN TAG #URR8PPP Breakpoints not being hit in JetBrains Rider? I am trying to set a breakpoint in JetBrains Rider, but the debugger isn't breaking. I know for sure the application should reach the code I'm trying to break on, as changing string literals appears in the program. I have completely reinstalled all my JetBrains programs (wiping settings). I've also tried every answer in this thread: break point is not hitting while debugging, with no luck. This bug doesn't occur in Visual Studio, but does occur with any project in Rider. It also doesn't happen on my other copy of Rider that I use on my other PC. I appreciate any help, thanks! By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

lldb cannot lookup symbol in imported dylib

Image
Clash Royale CLAN TAG #URR8PPP lldb cannot lookup symbol in imported dylib I am debugging a C program on arm64 with lldb and in order to implement my own debugging function I wrote a standalone debug helper program, compiled it as a dylib and imported it into lldb by using: (lldb) target modules add debugHelper.dylib (lldb) target modules add debugHelper.dylib However when I call the function declared in the dylib, lldb errors: (lldb) expression debugPrint() error: Couldn't lookup symbols: _debugPrint If I type in a random function name (e.g. foo): (lldb) expression foo() error: use of undeclared identifier 'foo' , which makes me believe importing the dylib is indeed successful, since debugPrint is not an undeclared identifier . debugPrint undeclared identifier // debugHelper.c #include <stdio.h> int debugPrint() { printf("%sn", "Debug info printed! n"); return 0; } debugHelper.dylib is compiled with: $ xcrun --sdk iphoneos cc debugHelpe...

Debugging the InitializeComponent function in the Visual Studio designer

Image
Clash Royale CLAN TAG #URR8PPP Debugging the InitializeComponent function in the Visual Studio designer In testing a number of changes to a custom WinForms control I'm encountering some issues which only occur when loading a form hosting the custom control in the Visual Studio designer. As a result, I'd like to understand if there is any method for debugging and stepping through (or logging in some way) the behaviour of the custom control's code when the Visual Studio designer loads. Well what's stopping you from just stepping into it as normal? I've just tried it and it seems fine. – Jon Skeet Feb 8 '14 at 21:54 I must be missing something obvious as the breakpoints in the custom control's code don't seem to be triggering when firing up the designer. – Chris Co...