Re: [RFC] [PATCH] ConnMan backtrace support

2010-08-17 Thread Marcel Holtmann
Hi Samuel, > > +static void signal_handler(int signo) > > +{ > > + switch (signo) { > > + case SIGSEGV: > > + case SIGBUS: > > + case SIGILL: > > + case SIGABRT: > > + connman_info("Aborting (signal %d)", signo); > > + __connman_log_backtrace(); > > + exit(1

Re: [RFC] [PATCH] ConnMan backtrace support

2010-08-17 Thread Marcel Holtmann
Hi Samuel, > Add a generic signal handler in order to dump ConnMan backtrace when > crashing. The implementation is based on glibc backtrace() routines and > thus can not resolve static function names. A little python wrapper over > addr2line fixes that by generating a full backtrace from a comple

Re: [RFC] [PATCH] ConnMan backtrace support

2010-08-17 Thread Kalle Valo
Samuel Ortiz writes: > Add a generic signal handler in order to dump ConnMan backtrace when > crashing. This is really nice. Makes my life easier, thanks :) The backtrace is dumped to the syslog, right? That way it's easy to access. -- Kalle Valo __

[RFC] [PATCH] ConnMan backtrace support

2010-08-16 Thread Samuel Ortiz
Add a generic signal handler in order to dump ConnMan backtrace when crashing. The implementation is based on glibc backtrace() routines and thus can not resolve static function names. A little python wrapper over addr2line fixes that by generating a full backtrace from a complete connman log file