Re: [Warzone-dev] What additional information do we need to add to the crash handler dump file ?

2009-06-15 Thread Per Inge Mathisen 
On Mon, Jun 15, 2009 at 3:24 PM, Christian Ohmchr@gmx.net wrote:
 On Monday, 15 June 2009 at  0:40, bugs buggy wrote:
 In order to alleviate this as much as possible, I have modified the
 crash handler dump file to spit out the openAL  openGL vendor/version
 strings.

 I was thinking about how to handle that in a nice way with C strings, but just
 using C++ strings is of course nicer.

You should not allocate anything on the heap in a crash handler. Make
sure all buffers are allocated in advanced and just fill them in
C-style.

 All these things can't be added to the crash dump file with the
 addDumpInfo(), since that will remember the last settings as well, (as
 in, they play X map, we store X map, they play Y map, we have X map
 and Y map in stream...) will have to have another section, and clear
 the stream first, then add everything again, unless someone can think
 of another way?

 Just keep everything? Sometimes a crash happens because of remaining crap from
 an old map. Gives at least some of the history, and not only the momentary
 snapshot we get now.

Wrong information can be worse than no information.

  - Per

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] What additional information do we need to add to the crash handler dump file ?

2009-06-15 Thread Christian Ohm 
On Monday, 15 June 2009 at 16:27, Per Inge Mathisen wrote:
 Wrong information can be worse than no information.

In which scenario do you see this giving wrong information? Outdated perhaps,
but with timestamps we know how much time passed between the last message and
the crash. And of course it doesn't replace a good bug description, but how
often have you seen one with a crashdump?

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] What additional information do we need to add to the crash handler dump file ?

2009-06-15 Thread bugs buggy 
On 6/15/09, Christian Ohm chr.x...@gmx.net wrote:
 On Monday, 15 June 2009 at  0:40, bugs buggy wrote:
   In order to alleviate this as much as possible, I have modified the
   crash handler dump file to spit out the openAL  openGL vendor/version
   strings.

  Though I'd put the OpenXX strings right after the first info block, without 
 any
  separators (and minus a few newlines after the machine line).

Everything above the PhysicsFS version info, is done before we hit
almost all init routines.

   All these things can't be added to the crash dump file with the
   addDumpInfo(), since that will remember the last settings as well, (as
   in, they play X map, we store X map, they play Y map, we have X map
   and Y map in stream...) will have to have another section, and clear
   the stream first, then add everything again, unless someone can think
   of another way?


 Just keep everything? Sometimes a crash happens because of remaining crap from
  an old map. Gives at least some of the history, and not only the momentary
  snapshot we get now.

Ok, that is how we will handle it.


   Oh, and sadly, this information will not be in the mac crash dump
   file...for the reasons stated before.  :(


 What exactly are those reasons?

On the mac, we don't use the same handler, and I am not in a position
to experiment to fix this.



This is what ours looks like now:
Program: ./src/warzone2100(warzone2100)
Command line: ./src/warzone2100 --window
Version: Version TRUNK r7742 (modified locally) - Built Jun 15 2009 - DEBUG
Distributor: UNKNOWN
Compiled on: Jun 15 2009 22:42:34
Compiled by: GCC 4.3.2
Executed on: Mon Jun 15 23:00:56 2009
Operating system: Linux
Node name: XyZ
Release: 2.6.26-2-486
Version: #1 Thu Mar 26 00:13:41 UTC 2009
Machine: i686

Pointers: 32bit

Compiled against PhysicsFS version: 1.1.1
Running with PhysicsFS version: 1.1.1

Misc Data:
[11:00:57]OpenGL Vendor : ATI Technologies Inc.
[11:00:57]OpenGL Renderer : ATI RADEON 9600 Series
[11:00:57]OpenGL Version : 2.1.8543 Release
[11:00:57]OpenAL Vendor: OpenAL Community
[11:00:57]OpenAL Version: 1.1
[11:00:57]OpenAL Renderer: OpenAL Soft
[11:00:57]Using language: English
[11:01:06]Current Level/map is CAM_1A
[11:01:22]User has used cheat code let me win
[11:01:30]Current Level/map is CAM_1B
[11:01:36]User has used cheat code let me win
[11:01:41]Current Level/map is SUB_1_1S
[11:01:45]User has used cheat code double up
[11:01:53]User has used cheat code biffer baker
[11:02:02]User has used cheat code let me win
[11:02:42]Current Level/map is Sk-Basingstoke-T2
[11:05:10]Current Level/map is CAM_1A
[11:05:31]User has used cheat code let me win
[11:05:38]Current Level/map is CAM_1B
[11:07:08]User has used cheat code showorders
[11:09:05]User has used cheat code give all
[11:10:09]User has used cheat code let me win
[11:10:14]Current Level/map is SUB_1_1S
[11:10:20]User has used cheat code let me win
[11:10:26]User has used cheat code let me win
[11:10:37]User has used cheat code let me win
[11:10:55]Current Level/map is SUB_1_1
[11:11:14]User has used cheat code let me win
[11:11:19]Current Level/map is SUB_1_2S
[11:11:28]Current Level/map is SUB_1_2
[11:11:35]User has used cheat code let me win
[11:11:40]Current Level/map is SUB_1_3S
[11:11:53]Current Level/map is SUB_1_3

Dump caused by signal: SIGSEGV: Invalid memory reference: Address not
mapped to object

...

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

[Warzone-dev] What additional information do we need to add to the crash handler dump file ?

2009-06-14 Thread bugs buggy 
For those of us that read the tickets, they suffer for a severe case
of 'need info'.

In order to alleviate this as much as possible, I have modified the
crash handler dump file to spit out the openAL  openGL vendor/version
strings.

I also plan to add map name, if cheats were used, and texture size
(what the user has it set to), and I am wanting to add what language
wz is set to, by using getLanguage() --which I think should work.

All these things can't be added to the crash dump file with the
addDumpInfo(), since that will remember the last settings as well, (as
in, they play X map, we store X map, they play Y map, we have X map
and Y map in stream...) will have to have another section, and clear
the stream first, then add everything again, unless someone can think
of another way?

Is there anything else that we need to be in the report?  WZ has
plenty of globals... ;)


Oh, and sadly, this information will not be in the mac crash dump
file...for the reasons stated before.  :(

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev