We use CFrameWnd in extension DLL for some application, the MFCMenuBar::CreateFromMenu(...) is used to add menu bar. Everything works well.
But if some manipulations with the menu were performed and then main app exited it crashes somewhere in ntdll. Happens only in Debug build.
If menu is not not touched, the app does not have any issues. Any clue what can it be? Some conflict of menus with main app frame?
Related
I was thinking that on macOS, you get a cool crash reporter that shows up when an application crashes. I wanted to force that with my app, that has a "Test Crash" button in a Tray Menu application (electronJS), and show a custom error message. If not, just making the app freeze up/hang would be good.
I was thinking about running a resource-heavy command that got looped super fast but that might use all the computer resources and then it'd be the one that crashes.
Is there any way to do this without process.exit()?
From this diagram I understand that the last step of the bootup process has the window manager launching the Gaia home screen.
I want to experiment and change the the first app that is booted and whatever launches when the home button is pressed, but I have not been able to figure out exactly where is that the homescreen app first launched.
Any pointers would be greatly appreciated.
There is a setting called homescreen.manifestURL that points to the manifest URL of the application that is used as homescreen. You can grep this string to know where exactly it's used.
This setting is set at build time in build/settings.js. You can try to change it there.
You can also install a separate homescreen app (see https://github.com/KevinGrandon/firefoxos-homescreen-boilerplate for a boilerplate for a homescreen -- I'm not sure how uptodate it is) and enable it from the Settings app. It has a "role": "homescreen" property in its manifest.
Before the recent firmware update, web-based debugging (at port 9222) would persist between activities. Now any transition, say from the home screen to my app, stops the debugger with a message at the top saying...
Detached from the target
Remote debugging has been terminated with reason: target_closed.
Please re-attach to the new target.
It's not a huge problem to start a new debug window, but I'm worried that if the debugger isn't running when my app is loaded I won't get the benefit of the "Disable cache (while DevTools is open)" option.
Any details or workarounds would be appreciated.
UPDATE
Confirmed! In my case at least, the debugger stops with the above error and the latest version of my html, javascript, etc. does not get loaded
Try this as a work around and see if it works: when your page is loaded, run window.location.reload() in the debug console to reload the page (so you get a full debugging info from the beginning without missing anything) or window.location.reload(true) to do the same and clear cache as well.
I have not found a good simple tutorial for this. I just want the app to freeze at the breakpoints so I can explore the contents of the various variables, particularly their json content.
This is a garbage documentation:
http://www.jetbrains.com/webstorm/webhelp/running-and-debugging-node-js.html#d40161e701
I can't even set up breakpoints. Is it so simple to do this in Eclipse...
UPDATE
Using Webstorm 7.0's early access build, the debugger works flawlessly. I just made a new project, added a breakpoint and used Debug. Stopped at that breakpoint with no problems whatsoever, so apparently Webstorm 6.0's debugger sucks :D
You can get it here: http://confluence.jetbrains.com/display/WI/WebStorm+7+EAP Beware, it expires on 8 August.
I use webstorm and it's great. Having looked at that documentation, I agree. If you're just starting out, you don't need all the remote and attach to existing processes options.
The easiest option would be to rightclick on your main js file and choose debug. Setting breakpoints is the same as in most editors these days, just click left of the line.
If you don't get the debug option when you right click then you need to make a run/debug configuration which sounds worse than it is.
Select "Run" -> "Edit configurations".
Click the plus sign.
Choose "Node.js"
Click on the browse ... button on the Path to Node App js file and choose the file you want to debug
Click Ok.
Click on the bug!
When attempting to debug (Run -> Debug), the "waiting for debugger" dialog appears, and subsequently disappears. The simulator starts up to the home screen, I click on my app, and all that happens is a black screen appears. No breakpoints are hit, and the application never appears to do anything. Simply running the application without debugging works as expected. Any ideas?
If you haven't fixed this already - the same thing happened to me. And as Driss says in the comments having a folder called Resources in your project gives the iPhone Simulator a heartattack and crashes it from the looks of things, without even copying your app bundle to the simulator directory.
I think I had a very similar issue. Did this happen with your project "all of a sudden?", did you rename your View's .xib file? did you have a NavigationController then delete it and now have this issue?
Can you also please post your "FinishedLaunching" code from your Main.cs please.
Driss.