I have a Cloud Run application that crashes with a mysterious exception. For reasons (Mac Silicon...) I can't test locally, only deploy new versions on Cloud Run.
When I POST the offending request, I get back an internal error and I see a log TIMESTAMP Exception in thread "main". Unfortunately, the rest of the stack trace does not get printed in the log line, either in the service or in the log explorer. Is there a way to get it to print the entire stack trace?
I am going to pepper my service with log lines but I was hoping to also figure out how to see the exception too.
Related
we have a windows 8.1 app in the windows store that sometimes crashes or hangs and we are unable to receive reports about hangs and crashs reported by the user via the store.
Collecting of telemetriy data is enabled in the store like mentioned in this MSDN-Article(http://msdn.microsoft.com/en-us/library/windows/apps/hh967787.aspx).
So I did a crash of the app by myself, took a look in the WER-ReportArchive(%localappdata%\Microsoft\Windows\Windows Error Reporting) and found a .cab & .wer-file. So I think the report was sended to microsoft, but theres still no crash or hang documented in the Dashboard of the App Store.
I tried to get a crashdump via Windows Error Reporting - LocalDumps (msdn.microsoft.com/en-us/library/ bb787181%28VS.85%29.aspx), but this dump is only generated when an error occurs.
In my case mostly the app just hangs!
I also tried to configure Windows Error Report - Registry Entries (http://msdn.microsoft.com/en-us/library/bb513638%28VS.85%29.aspx), but it seems most of the entries are just ignored.
I noticed WER is creating a dump-file of AppHangs as well, before sending the data to Microsoft (memory.hdmp in ReportQueue). But this files are deleted immediately after sending.
Does somebody know a way to get memory dumps and further information for AppHangs as well?
Thanks in Advance.
I think you could use the posibility of Just-In-Time or postmortem debugging via setting registry key for AeDebug, if you can create the crash.
Have a look at:
Improving apps with Quality reports
https://blogs.msdn.microsoft.com/windowsstore/2012/06/27/improving-apps-with-quality-reports/
Debugging a Windows 8.1 Store App Crash Dump
https://blogs.msdn.microsoft.com/ntdebugging/2014/01/13/debugging-a-windows-8-1-store-app-crash-dump/
Configuring Automatic Debugging https://msdn.microsoft.com/en-us/library/bb204634(vs.85).aspx
Using WER: Collecting User-Mode Dumps https://msdn.microsoft.com/en-us/library/bb787181(v=vs.85).aspx
Enabling JIT-Attach Debugging https://msdn.microsoft.com/en-us/library/2ac5yxx6.aspx
I have a WP8 App where I want to store the crash logs if and when generated.
Is there any way of fetching the crash dump file from Windows Phone 8 programmatically?
As far as I know, you can't retrieve the crash dumps that are automatically sent to the DevCenter. However, what you can do is subscribing to the global unhandled exception event handler, store the exception contents in the isolated storage, then do whatever you need with it (like sending it to a remote server). That's what many applications do, and it's even automated by some libraries (such as Telerik).
You can achieve that by using a logging system as MetroLog. You'll be able to collect these crash logs if you configure GlobalCrashHandler that will ensure that a FATAL log entry is written if an unhandled exception occurs.
You can install it using NuGet
Install-Package MetroLog
Here's an quick example:
using MetroLog;
using MetroLog.Targets;
LogManagerFactory.DefaultConfiguration.AddTarget(LogLevel.Trace, LogLevel.Fatal, new FileStreamingTarget());
GlobalCrashHandler.Configure();
ILogger log = LogManagerFactory.DefaultLogManager.GetLogger<MainPage>();
log.Trace("This is a trace message.");
You can find a tutorial explaining how to add it on your project at http://talkitbr.com/2015/06/11/adicionando-logs-em-universal-apps. Also there is an explanation regarding retrieving these logs.
When I was validation my Windows Store App I got the following error:
Application Error: Application Launch was not detected for application
App. This could be because your application failed to launch
correctly. Please consider re-running the test and avoid interacting
with the application while tests are running.
What does this mean? The app will not validate.
I thought it was a bit weird and I couldn't find anything when I googled it but people who had almost the same problem as me, though rather than launching it was failing to sleep. This was just plain odd.
I tried to launch the app from Visual Studio 2012 just to prove to myself that it did start properly and for some crazy reason it didn't work. I usually test the game on my Local Machine rather than the Simulator but now, for some reason, it was set to the Simulator and I have been having problems getting it to start lately (the simulator).
I changed it back to the local machine and ran the tests again. This time it worked.
So, if you get this error it might be time to see if your simulator works and if not, have the Local Machine set as default to run with.
I am using visual studio 2005. When I debug and reached at exception point. I got following error dialouge.
message screenshot
When I click No, I got following error page.
The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.
Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.
I also checked the eventvwr log and it says:
**aspnet_wp.exe (PID: 3584) stopped unexpectedly.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.**
Please help me.
I can't see your image (hotlinking to that site isn't allowed), but I'm guessing that when you hit "No", you're telling ASP.NET that you don't want to debug the exception, so it's letting it bubble up to the browser, which shows you the "Webserver unavailable" that you're seeing. If you debug your error, what do you get?
Also, please fix your image so we can see your dialog box.
What does it mean:
"First-chance exception at in : 0x000006BA: The RPC server is unavailable"
?
this debug message appears in Debug output of visual studio debugger when I using socket connection, but I don't know what operation initiates this message...
"First-chance exception" occurs when the exception is thrown, before anyone catches it. Usually, these are benign, and can be ignored (because someone is going to catch it).
You can get the debugger to break when the exception is thrown, whether or not someone later catches it.
In Visual Studio, this is done by choosing Debug / Exceptions and putting a check in the "Thrown" column for the exceptions you're interested in. Then, when the exception is thrown, the debugger will break at the relevant place.
Note that you might end up in the middle of nowhere (i.e. in disassembly), so make sure that you've got your debugging symbols configured correctly.
Also note that some exceptions aren't in the list by default, so you'll have to click the "Add..." button in that dialog.
This is most likely a bug (see these threads: 1 and 2).
I get this when debugging a C# application that calls into a COM object written in C++ when the COM object calls WNetOpenEnum (which succeeds, by the way). My system is Windows 7 x64 SP1 and fully patched, Visual Studio 2010. It happens regardless if VS is started as elevated process or normally.
The debugger reports you likely have not enabled remote debuggimg.
Check if you have Remote Procedure Call service enabled and running (MMD.exe process). This service is required by remote debugging feature.
You may try to follow How to turn on remote debugging