You should now be able to get more details in a gdb backtrace, since you have all debug symbols and no optimization.
- Bug#1030659: xscreensaver: segfault when starting ... Tormod Volden
- Bug#1030659: xscreensaver: segfault when start... Marco
- Bug#1030659: xscreensaver: segfault when s... Tormod Volden
- Bug#1030659: xscreensaver: segfault w... Marco
- Bug#1030659: xscreensaver: segfau... Tormod Volden
- Bug#1030659: xscreensaver: segfau... Marco
- Bug#1030659: xscreensaver: segfau... Tormod Volden
- Bug#1030659: xscreensaver: segfau... Marco
- Bug#1030659: xscreensaver: segfau... Tormod Volden
- Bug#1030659: xscreensaver: segfau... Marco
- Bug#1030659: xscreensaver: segfau... Tormod Volden
- Bug#1030659: xscreensaver: segfau... Marco
- Bug#1030659: xscreensaver: segfau... Tormod Volden
- Bug#1030659: xscreensaver: segfau... Jamie Zawinski
- Bug#1030659: xscreensaver: segfau... Tormod Volden
- Bug#1030659: xscreensaver: segfau... Tormod Volden
- Bug#1030659: xscreensaver: xscree... Tormod Volden
- Bug#1030659: xscreensaver: segfault when starting xscreensa... Mamoru TASAKA
- Bug#1030659: xscreensaver: segfault when starting xscr... Jamie Zawinski
- Bug#1030659: xscreensaver: segfault when starting xscr... Tormod Volden
- Bug#1030659: xscreensaver: segfault when starting ... Jamie Zawinski