exception-handling

I use CherryPy to run a very simple web server. It is intended to process the GET parameters and, if they are correct, do something with them. import cherrypy class MainServer(object): def index(self, **params): # do things with correct parameters if 'a' in params: print params['a'] index.exposed = True cherrypy.quickstart(MainServer()) For example, http://127.0.0.1:8080/abcde: 404 Not Found The path '/abcde' was not found. Traceback (most recent call last): File "C:\Python27\lib\site-packages\cherrypy\_cprequest.py", line 656, in respond response.body = self.handler() File "C:\Python27\lib

I'm trying to get started with this library: 32feet I have a Broadcomm Bluetooth Stack and haven't been able to figure out how to get this library set up. When I run my code, I get: Unhandled Exception: System.PlatformNotSupportedException: No supported Bluetooth protocol stack found. After digging around on their site, I found this: Installation instructions It says to copy the appropriate DLL's into the project and then run the Test32FeetWidcommWin32.exe . I've tried putting the files in every single folder in my Visual Studio project and then running that EXE, but I still get the same error

Is it possible to re-throw an exception without losing the back-trace in gdb? Or is there a way in gdb to "back up' a few lines and back trace from there? I'm on GDB 7.7.1, the most recent. I sometimes find myself running into situations like this, needing a back trace from the original throw of the exception, and needing to comment out the try/catch parts, recompiling, and re-running in gdb. try { someFuncThatCanThrowException(); } catch(exceptionType& exception) { if(@CAN_RECOVER@) { ... } else { throw; } } ----OR---- try { someFuncThatCanThrowException(); } catch(exceptionType& exception) {

Let's say I have the following Java interface that I may not modify: public interface MyInterface { public void doSomething(); } And now the class implementing it is like this: class MyImplementation implements MyInterface { public void doSomething() { try { // read file } catch (IOException e) { // what to do? } } } I can't recover from not reading the file. A subclass of RuntimeException can clearly help me, but I'm not sure if it's the right thing to do: the problem is that that exception would then not be documented in the class and a user of the class would possibly get that exception an

I have run into a rather weird little problem. In the following code I can not understand how e can be null ; try { //Some Code here } catch (Exception e) { //Here e is null } As far as I know, throw null will be converted to throw new NullReferenceException() . The problem seems to be related to multithreading, as removing another thread also seems to fix it. Or at least I have only seen this when the above code is run in a new thread. The whole program uses many threads and is a bit complex. Anyway my question is, how can e be null? - Hopefully the answer to that can help find the source of

I don't know what the heck I'm doing wrong here, I wrote have an RPC client trying to connect to a non-existent server, and I'm trying to handle the exception that is thrown, but no matter what I try I can't figure out how I'm supposed to handle this: def _get_rpc(): try: a = ServerProxy('http://dd:LNXFhcZnYshy5mKyOFfy@127.0.0.1:9001') a = a.supervisor return a except: return False rpc = _get_rpc() if not rpc: print "No RPC" Since there is no server running, I would expect the output to be "No RPC" but instead I get an exception: Traceback (most recent call last): File "xmlrpctest.py", line 20

I consider to use Polly to create policy to log exception and rethrow. I didn't find an existing method that allow it out of the box , but some options that I see are Fallback // Specify a substitute value or func, calling an action (eg for logging) if the fallback is invoked. Policy.Handle<Whatever>() .Fallback<UserAvatar>(UserAvatar.Blank, onFallback: (exception, context) => { _logger.Log(exception, context); throw exception; }); Question: is it ok to throw exception from Fallback? Timeout Policy.Timeout(1, T30meoutStrategy.Pessimistic, (context, timespan, task) => { task.ContinueWith(t => {