Re: [Warzone-dev] Linux crashdumps

2007-02-22 Thread Christian Ohm
On Thursday, 22 February 2007 at 10:40, Per Inge Mathisen wrote: Also see info Backtrace glibc. The best would be to automatically connect gdb to the program and give a bt full dump. If you automatically emailed that back to us, it would be an invaluable debug aid, and a massive privacy

[Warzone-dev] Linux crashdumps

2007-02-21 Thread Dennis Schridde
Wrote a crashdumper for Linux which I will integrate alongside the minidumper for Windows. For those interested in signal handling and backtrace creation, this sample might be usefull. Package contains of an app which dumps the crash informations into mdump.gdmp and another app which retrieves

Re: [Warzone-dev] Linux crashdumps

2007-02-21 Thread Per Inge Mathisen
On 2/21/07, Dennis Schridde [EMAIL PROTECTED] wrote: For those interested in signal handling and backtrace creation, this sample might be usefull. Dump caused by signal: SIGSEGV, Segmentation fault Backtrace: 0x8048513 0x315420 0x8048995 0x4b8ae4e4 0x8048451 At

Re: [Warzone-dev] Linux crashdumps

2007-02-21 Thread Dennis Schridde
Am Mittwoch, 21. Februar 2007 schrieb Per Inge Mathisen: On 2/21/07, Dennis Schridde [EMAIL PROTECTED] wrote: For those interested in signal handling and backtrace creation, this sample might be usefull. Dump caused by signal: SIGSEGV, Segmentation fault Backtrace: 0x8048513

Re: [Warzone-dev] Linux crashdumps

2007-02-21 Thread Dennis Schridde
Am Mittwoch, 21. Februar 2007 schrieb Dennis Schridde: Am Mittwoch, 21. Februar 2007 schrieb Per Inge Mathisen: On 2/21/07, Dennis Schridde [EMAIL PROTECTED] wrote: For those interested in signal handling and backtrace creation, this sample might be usefull. Dump caused by signal: