I am trying to solve an issue in my application which is abruptly crashing whenever the application use 'MIngliu' font. In order to solving and finding that bug I tried to dedug the WinCE6.0 OS kernel, and found in the output window that "DEBUGCHK" macro is failing in fontfile.cpp. But the problem is that fontfile.cpp is not available with us.So please suggest what can be done inorder to fix that issue if it is a part of kernel..Here I am also attaching the snapshot of the output window of visual studio.The last line of the window is showing the error..
Related
A user that works in my company has an Error 13 Type mismatch in the moment that she wants to input some data in a grid.
The thing is that when she has that problem, my application only shows the error screen and nothing more (I mean it doesn't say where the error occurs).
I want to know if there is a way that I can "see" the problem in a debug application because I don't have the source code of my application in this computer and I don't know if the problem is because of a Windows configuration issue or why this error pops up provided that when she uses another terminal, different to the one that she normally uses, she can do her job without problems (they have the same settings in the two pcs).
I have the source code in my terminal but as say above, in my terminal the error doesn't pop up so I need to see it in her terminal.
How can I do this?
When I try to open a .ui form in Qt Creator, it crashes.
Here's some strings from a crash report:
Application Specific Information:
terminating with uncaught exception of type std::bad_alloc:
std::bad_alloc abort() called
Does anyone know what to do? If so, help me out, please.
OK, here's the solution:
I have reinstalled the OS and Qt with all its parts works properly.
If someone has the same problem and has a Time Machine archive, do not restore from it, 'cause if you do, the bug will remain. Instead of that, install OS X and then restore files from Finder, if necessary.
Where XCode generate error for application crash ?
I'm crazyng ! My application when open second file xib with webview then it crash. But I don't know why ? how can i Know where is error ?
You need to learn how to use the debugger in Xcode.
Run your app under the debugger then instead if simply getting a stack trace Xcode will stop at the line the fault occurs and show you your code and variables. You can then examine the contents of your variables, the call tree, etc. and hunt down the problem.
Once you know the general area of the problem you can place breakpoints to pause your application before the problem occurs and check whether your variables have the values expected etc. Then you can run till the next breakpoint, or step through your code a line at a time.
You can add code, such as NSAssert's and NSLog's to your app to check progress and display information without stopping the run, etc.
It's a process, and some problems will be harder to track down, but you'll get quicker at it with practice.
The Xcode documentation will tell you all about the debugger.
HTH
The only error I ever get is SIGABRT in main. This is getting incredibly frustrating as I have to guess what line caused the error and why.
This is a far cry from visual studio's informative error messages. It's basically like sending off an entire novel to an editor and the only notes you get back are: "There is a problem somewhere in your book. There may be many or just one and they are either gramatical or to do with spelling."
I just don't know how anyone can work like this. What am I doing wrong? Surely I'm missing something essential.
Write some NSLog() into your code and you'll see it in the console. It's a great help to narrow down a crash.
if you have encountered memory problems (aka – your app crashes for no apparent reason because you attempted to use an object that you deallocated to soon) setting NSZombieEnabled = YES can help you diagnose the problem.
Normally, when your app crashes in this way and you look at the log it tells you nothing (thanks Apple!). However, if you select your executable (under Executables in Xcode), hit the info button (round blue thing at the top), select arguments and put this in the bottom screen NSZombieEnabled = YES the log will give you more information.
Now, if your app crashes the log will have an indication of the object you attempted to access that has already been deallocated. Not forget to turn it off before you deploy it – you don’t want a bunch of nszombies running around your clients phones…
http://howtomakeiphoneapps.com/nszombie-and-xcode-oh-my/27/
This is driving me crazy. I'm working on a C# Forms application that is crashing for some reason when calling _documentList.Items.Clear();. For some reason, Visual Studio never catches the crash and it acts as if the application closed without any errors. I'm in the debugger stepping through line by line, and as soon as I hit the _documentList.Items.Clear();, the debugger stops and the form closes. Please help!
Edit: I've found why the app was crashing, but I'm still not sure why the debugger isn't catching it. This should have been much easier to find than it was.
I was trying to update my GUI from a FileSystemWatcher event, so I had to use this.InvokeRequired and this.Invoke(). I'm no longer getting the crash, but I would still like to know why VS isn't catching this in the debugger. My understanding is I should have been getting an exception with the message "Cross-thread operation not valid:"
I think we don't have listbox.Clear() it shopuld be listbox.Items.Clear();
Have you checked if the listbox have items before stepping into the line where you are clearing the items.
Check the items count of listbox.
It appears that this is a known issue and has been fixed when using Tasks in .NET 4.0. See this question (InvokeRequired Exception Handling) for more info.