raygun

How to catch non-MVC and non-REST exceptions in Spring Boot

由 こ雲淡風輕ζ 提交于 2020-01-23 08:09:27
问题 I've been able to find endless amounts of tutorials on how to catch unhandled exceptions in Spring MVC or Spring REST, but what I want to know is how to catch unhandled exceptions without using the Spring Web framework at all. I am writing an application which does not have a web component, and I am not going to import Spring Web only for exception handling. When a @Service throws an exception that goes unhandled, I need to catch it so that I can log it properly to Raygun. For example,

Why do my stack traces only include line numbers if the debugger is attached?

由 懵懂的女人 提交于 2019-12-01 23:53:12
问题 I have a Xamarin.Android application that reports crashes to Raygun. The stack traces reported to Raygun from Release builds do not include line numbers. If I give the Release build configuration the same settings as the Debug configuration in the .csproj file: <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' "> <DebugSymbols>True</DebugSymbols> <DebugType>full</DebugType> <Optimize>false</Optimize> ... </PropertyGroup> then I still don't see line numbers in the

Why do my stack traces only include line numbers if the debugger is attached?

由 ♀尐吖头ヾ 提交于 2019-12-01 21:59:21
I have a Xamarin.Android application that reports crashes to Raygun. The stack traces reported to Raygun from Release builds do not include line numbers. If I give the Release build configuration the same settings as the Debug configuration in the .csproj file: <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' "> <DebugSymbols>True</DebugSymbols> <DebugType>full</DebugType> <Optimize>false</Optimize> ... </PropertyGroup> then I still don't see line numbers in the stack traces sent to Raygun. However, if I run the app with the Visual Studio debugger attached, then
订阅 raygun