| 2007-02-05 14:01:44 |
Phil Housley |
bug |
|
|
added bug |
| 2007-02-05 14:18:13 |
Sebastien Bacher |
gnome-system-tools: status |
Unconfirmed |
Needs Info |
|
| 2007-02-05 14:18:13 |
Sebastien Bacher |
gnome-system-tools: assignee |
|
desktop-bugs |
|
| 2007-02-05 14:18:13 |
Sebastien Bacher |
gnome-system-tools: statusexplanation |
|
Thank you for your bug. The packages have a -dbgysm variant containing the debug symbols you can install, that's described on https://wiki.ubuntu.com/DebuggingProgramCrash. A crash to alloc looks like a memory corruption. Could you try to get a valgrind log (https://wiki.ubuntu.com/Valgrind) for the problem? |
|
| 2007-02-05 14:44:32 |
Phil Housley |
bug |
|
|
added attachment 'valgrind-logs-network-admin.tar.gz' (Valgrind memcheck log) |
| 2007-02-05 15:33:35 |
Phil Housley |
bug |
|
|
added attachment 'gdb-network-admin.txt' (gdb trace with pango sybols) |
| 2007-02-13 11:14:21 |
Sebastien Bacher |
gnome-system-tools: status |
Needs Info |
Fix Released |
|
| 2007-02-13 11:14:21 |
Sebastien Bacher |
gnome-system-tools: statusexplanation |
Thank you for your bug. The packages have a -dbgysm variant containing the debug symbols you can install, that's described on https://wiki.ubuntu.com/DebuggingProgramCrash. A crash to alloc looks like a memory corruption. Could you try to get a valgrind log (https://wiki.ubuntu.com/Valgrind) for the problem? |
right, that was probably due to the memory corruption which has been fixed with 2.17.91 |
|
