exception-handling

I'm trying to catch an exception thrown from a task method using ContinueWith and OnlyOnFaulted like below. However I get an unhandled exception while I try to run this code. I'd like the task to run to completion since I have handled the exception already. But Task.Wait() runs into AggregateException. var taskAction = new Action(() => { Thread.Sleep(1000); Console.WriteLine("Task Waited for a sec"); throw (new Exception("throwing for example")); }); Task t = Task.Factory.StartNew(taskAction); t.ContinueWith(x => Console.WriteLine("In the on Faulted continue with code. Catched exception from

I'm working on an application where the process goes on like this UI --> backend process --> result to UI. In my Java code, I have handled my exceptions using try-catch, But in the code I have so many repeated exceptions that may throw same exceptions in different classes, which reduces the readability and code reuse. So, I am planning to do a exception handling strategy so that instead of throwing the same exception in different classes, I need to organize the exception and reuse the exception codes. Could anyone suggest me best exception handling technique to do this? Always handle Unchecked

I want to call a function that may throw an exception. If it does throw an exception, I want to catch it and pass the exception object to a handler function. The default implementation of the handler function is simply to throw the exception. Here is whittled-down code to illustrate the issue: struct base_exception : exception { char const* what() const throw() { return "base_exception"; } }; struct derived_exception : base_exception { char const* what() const throw() { return "derived_exception"; } }; void exception_handler( base_exception const &e ) { throw e; // always throws a base

Mixed mode C++ project. Native code is calling managed code. Managed code might throw an exception. I can catch said exception in native mode using a vectored exception handler; I can see its PEXCEPTION_POINTERS . The telling code 0xE0434F4D, meaning it's a CLR exception, is there. Question: is there any way to get any sensible information (exception class, message, stack trace etc.) from the attendant data? There's one parameter in the ExceptionInformation , and it looks like a pointer to something... No, that's too late. All you got is the exception code. You might get something in

The title may be a little confusing so I'll explain. Say you had this call chain... public DoWork(index) >> private DoWorkHelper(index) >> private CheckIndex(index) Now if you call DoWork , it traverses the calls down to CheckIndex , adding each deeper call to the call stack. Now if someone calls DoWork with a bad value for index , it throws the exception all the way down at CheckIndex , and currently, that's where the debugger breaks. You then have to walk back up the call stack to see the real offender was that someone passed bad data to DoWork . Now back in the VB6 days, you could simply

I have a protractor setup with multiple browsers configured through multiCapabilities , running tests on browserstack. One of my key protractor specs/tests contain the following afterEach() block: afterEach(function() { browser.manage().logs().get("browser").then(function (browserLog) { expect(browserLog.length).toEqual(0); }); }); that checks that the browser console is empty (no errors on the console). The problem is : when I run this spec against Internet Explorer, I'm getting an UnknownError : UnknownError: Command not found: POST /session/6b838fe8-f4a6-4b31-b245-f4bf8f37537c/log After a

I am not sure about this answer. I cant find it anywhere. Is it the empty error handling?! It is known as suppressing the exception, or swallowing the exception. May not be a very good practice, unless commented with a very good reason. We affectionately call this "eating the exception" at work. Basically, it means that something bad occurred, and we are burying our head in the sand and pretending it never happened. At the very least, a good practice is to have a logger.error(e) within that block: try { // code here } catch (Exception e) { logger.error(e); } so that you will have it recorded