On Tue, 2009-08-04 at 09:53 -0400, Carolyn Beeton wrote: > I'm asking about debugging core files from the field on the list because > I foresee a lot of it in my future and there must be some pointers out > there. > > If someone gives me just a corefile, is there anything I can do with it? > My dev environment is pretty much 100% guaranteed not to match theirs > (since mine is 64bit) so gdb doesn't provide any useful info. > > sipx-snapshot has a --core option, but that is not exposed in the > sipXconfig GUI. Also, it looks like that option will not actually > collect the backtraces. Could we add that capability? (We have a fancy > --generate-core-files option which will collect backtraces from running > processes - something similar tied to --core would be very useful, or is > it already there and I am missing it?)
The option collects the executable and all shared libraries that it links with. You can then use options on gdb to load the core file and use those executables to resolve the symbols, just as though you're on the system that crashed. Dale originally worked out how to do this - did you create a wiki page on it, Dale? (if not, it would be a good idea). _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
