I have a CodeIgniter project which has some errors and I am trying to debug it. However, when I start debugging the debugger exits because MY_Controller which is extended by all controllers was not found.
The error on the console is like this:
Fatal error: Class 'MY_Controller' not found.
MY_Controller is in the application core folder and extends the CI_Controller. Why cant the debugger locate this class?
Apparently without solving this I cant debug my files. Otherwise the error does not pop up when I run the project without the debugger listening. I am using xdebug and PhpStorm.
Related
No matter what I do, I cannot get Rider to use Chrome for debugging. I've removed all other browsers listed and even set a "Custom path" to Chrome. I also have the required plugins installed and enabled; still, it starts up with:
Opening <URL> using the default OS app (=Edge)
It then starts logging errors like below:
Debugger listening on ws://...
Debugger attached.
Waiting for the debugger to disconnect...
About to exit with code: 0
Process terminated before summary could be written, possible error in async code no continuing!
Trying to exit with exit code 1
Process finished with exit code 0
The app consists of multiple SharePoint Framework (SPFx) React projects wrapped in netstandard2.0 class library projects. Each has a gulp file and I've created corresponding run/debug configurations similar to the below sample:
What do I need to do to get Rider to use Chrome?
In Gulp run configuration, you can't specify a browser to be used for debugging, neither you can debug the front-end app that runs in browser using this configuration. I suppose, it's your Gulp task that opens your system default browser once your app is started - the IDE has no control over this.
Anyway, to attach the debugger to the application that runs in browser, you need using JavaScript Debug run configuration with your server URL. In this configuration, you need to specify a browser to be used (the IDE will use Chrome there by default)
Also, I'd suggest removing --inspect option from Node options: in Gulp run configuration - it makes no sense here unless you are going to debug your Gulp task itself.
I'm working on a Direct2D (XAML) application (I picked this because I haven't done it before and I wanted to try it out, I thought it would be simple).
I created the project in Visual Studio 2012 using the default options.
I added a button to the GUI successfully.
I added a button press handler to the GUI successfully.
The problem is that I need the button press handler to send a registered windows message. I #include <Windows.h> as instructed by the MSDN docs for ::RegisterWindowMessage(), and finding the declaration and definition of the function with the F12 key works fine.
However, building the project fails, because the compiler can't find the function. Intellisense also flags the function as unrecognized.
I'm probably missing something in the project configuration, but I don't even know where to begin.
Can you please help me?
Edit: The exact error messages that I'm getting are:
error C2039: 'RegisterWindowMessage' : is not a member of '`global namespace''
error C3861: 'RegisterWindowMessage': identifier not found
RegisterWindowMessage is not available in a UWP application (which is likely what you are targeting in a XAML application). If you look into WinUser.h, you'll find the declarations are wrapped inside a
#if WINAPI_FAMILY_PARTITION(WINAPI_PARTITION_DESKTOP)
guard. This API is available to desktop applications only. There is nothing you can do to make it work in a UWP application.
I have an app which uses SlideMenuControllerSwift. I've modified some code to see how to present different panels, then rolled back my changes.
When running the project I get SIGABRT fatal error: call of deleted method in console when SlideMenuControllerSwift is initializing. No other error messages are given.
The project's source control appears to be in exactly the same state as before
changes.
I did a "clean"
Reinstalled pods.
Deleted pods directory and made a clean install
Deleted app from device and ran again
Did a fresh checkout into a different folder
Updated cocoapods gem
Even modified the function to use self.addLeftGestures()
How do I debug an issue caused by cocoa pod throwing "fatal error: call of deleted method"?
UPDATE: seems like something is seriously broken with the functions inside that pod, calling another function within init causes bad access exception:
In my case, I had created a project scheme that uses the release build configuration:
In this configuration, if your project build settings does not allow testability in this release mode then setting custom breakpoints or app crashes do not let you debug properly and you are served the fatal error: call of deleted method
Solution:
Check the project build settings for "testability".
Ensure it is "Yes" for the build configuration you are testing under.
In my case, I temporarily enabled testability for Release by making it Yes.
For anyone seeing this error using SwiftUI on XCode 11.4 and trying to access a property on an ObservableObject subclass eg.
class Model: ObservableObject {
#Published var name = ""
}
class ModelSub: Model {}
let model = ModelSub()
// This line causes `fatal error: call of deleted method` on XCode 11.4
$model.name
// Instead do
model._name.projectedValue
See more details here
I am trying to open VB6 project and get this error in log file,
Line 190: Class SampleQueryControl.SampleCtrl of control SampleCtrl1 was not a loaded control class
Any idea why this error occurred?
I have a console app, and a class library.
I'm making changes to the class library (adding new methods, changing what methods do, etc) - Just regular stuff - nothing fancy.
In the console app - I'm calling methods from the class library - obviously to test the class library methods - again no rocket science here!
Both projects are targeting Framework 3.5 (This is because I have Sharepoint 2010 being referenced in class library)
Now:
When I debug the app using F5 - I've set a break point in the console app. When it steps through to the class library (using F11) I get a message saying source code has changed in a pretty lengthy dialog. If I click cancel - it then says No source code available.
I have found a work around to right click on project in solution explorer, then select debug -> create new instance.
But this is strange, never had this issue before, what can I do to get the debugger behaving normally. By normally I mean every time I hit F5 it should understand that the source code in the class library will almost surely have changed and I don't want any nags about this, or break point conditions never being met.
On a side note, never had this issue before, so an explanation as to why its happening would help a lot.
Thanks in advance
Update: the short version
Why do I have to manually tell the debugger to "create new instance" everytime I want to debug? If I don't hitting f5 debugs the source code of the last successful debug session.
Maybe your console application doesn't build second project? Try verifying that newest version of library is called.