debug log madness after segfault

[Ian Jackson]

Binary package hint: nautilus

As I report in bug 153381, I managed to get nautilus to segfault. This resulted in it spinning on the CPU while continuously writing the following message over and over again into nautilus-debug-log.txt:
 0x8177510 2007/10/16 19:10:32.9014 (USER): debug log dumped due to signal 11

nautilus (or whatever library it is using) should take steps to ensure that if a segfault occurs when writing the debug log, it doesn't then attempt once more to write the debug log.

[Pedro Villavicencio (pedro)]

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

[Sebastien Bacher (seb128)]

Not marking duplicate, the other bug is likely a specific crash, the log handler is broken and we should also fix that, confirming the issue

[Thomas Novin (thomasn80)]

Just had this issue my self. I have noticed it maybe 10-20 times before.

$ wc -l nautilus-debug-log.txt
26119 nautilus-debug-log.txt

$ tail -3 nautilus-debug-log.txt
0x8177510 2008/01/15 17:03:39.9329 (USER): debug log dumped due to signal 11
0x8177510 2008/01/15 17:03:39.9446 (USER): debug log dumped due to signal 11
0x8177510 2008/01/15 17:03:39.9563 (USER): debug log dumped due to signal 11

After I killed the nautilus process that took 100% CPU with -15 it stopped.

[Jürgen Barlag (matrox-email)]

My nautilus-debug-log.txt starts with:

===== BEGIN MILESTONES =====
0x81778c8 2008/01/19 10:30:14.9518 (GLog): "nautilus-metafile.c: metafiles" hash table still has 2 elements at quit time (keys above)
0x81778c8 2008/01/19 10:30:14.9518 (GLog): "nautilus-directory.c: directories" hash table still has 2 elements at quit time (keys above)
0x81778c8 2008/01/19 10:30:14.9519 (USER): debug log dumped due to signal 11
0x81778c8 2008/01/19 10:30:14.9701 (USER): debug log dumped due to signal 11

[Pedro Villavicencio (pedro)]

Thanks for the report, this is fixed on Hardy, feel free to re open it if is still an issue with latest Hardy package. thanks you.