2007-03-03 16:00:06 |
Nicolas_Raoul |
bug |
|
|
added bug |
2007-03-03 16:02:08 |
Nicolas_Raoul |
description |
Binary package hint: audacity
Whenever I close the Audacity GUI, everything seems to close as expected, except that I can see "Segmentation fault (core dumped)" in the terminal I launched Audacity from.
Running it under GDB gives this information:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222714704 (LWP 17827)]
0xb72f2c70 in ?? () from /usr/lib/libX11.so.6
(gdb) bt
#0 0xb72f2c70 in ?? () from /usr/lib/libX11.so.6
#1 0x084037d8 in ?? ()
#2 0xb73d513c in ?? () from /usr/lib/libglib-1.2.so.0
#3 0xbffa1710 in ?? ()
#4 0xb74111ec in ?? () from /usr/lib/libgdk-1.2.so.0
#5 0xb7397a4c in ?? () from /usr/lib/libX11.so.6
#6 0x00000000 in ?? ()
This backtrace does not look very interesting, there is no debugging symbols, I looked for a dev package in Synaptic but could not find one. I am available for more tests if someone wants.
By the way, I tried to use -dbgsym debug symbols as described on https://wiki.ubuntu.com/DebuggingProgramCrash but it does not work, because people.ubuntu.com is down. Is it a temporary problem with the server, or is this howto outdated ? |
Binary package hint: audacity
Ubuntu Feisty, up-to-date
Linux 2.6.20-9-generic #2 SMP
Whenever I close the Audacity GUI, everything seems to close as expected, except that I can see "Segmentation fault (core dumped)" in the terminal I launched Audacity from.
Running it under GDB gives this information:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222714704 (LWP 17827)]
0xb72f2c70 in ?? () from /usr/lib/libX11.so.6
(gdb) bt
#0 0xb72f2c70 in ?? () from /usr/lib/libX11.so.6
#1 0x084037d8 in ?? ()
#2 0xb73d513c in ?? () from /usr/lib/libglib-1.2.so.0
#3 0xbffa1710 in ?? ()
#4 0xb74111ec in ?? () from /usr/lib/libgdk-1.2.so.0
#5 0xb7397a4c in ?? () from /usr/lib/libX11.so.6
#6 0x00000000 in ?? ()
This backtrace does not look very interesting, there is no debugging symbols, I looked for a dev package in Synaptic but could not find one. I am available for more tests if someone wants.
By the way, I tried to use -dbgsym debug symbols as described on https://wiki.ubuntu.com/DebuggingProgramCrash but it does not work, because people.ubuntu.com is down. Is it a temporary problem with the server, or is this howto outdated ? |
|
2007-03-22 23:21:09 |
Nicolas_Raoul |
bug |
|
|
added attachment 'valgrind.log.9503' (Valgring log, running and exiting Audacity) |
2007-03-22 23:48:58 |
William Grant |
audacity: status |
Unconfirmed |
Confirmed |
|
2007-03-22 23:48:58 |
William Grant |
audacity: importance |
Undecided |
Medium |
|
2007-03-22 23:48:58 |
William Grant |
audacity: statusexplanation |
|
This has an impressive number of duplicates, and is probably the same as bug #87434. |
|
2007-03-23 07:18:41 |
Nicolas_Raoul |
title |
Audacity always crashes when closing |
Audacity always segfaults when closing |
|
2007-05-20 11:15:31 |
Emmet Hikory |
audacity: status |
Confirmed |
Needs Info |
|
2007-05-20 11:15:31 |
Emmet Hikory |
audacity: statusexplanation |
This has an impressive number of duplicates, and is probably the same as bug #87434. |
Could someone please retest this against audacity 1.3 built against wxwidgets2.6 (and GTK2+). I believe it has been fixed by the recent upgrade. |
|
2007-07-05 10:08:21 |
Sebastien Bacher |
audacity: status |
Incomplete |
Invalid |
|
2007-07-05 10:08:21 |
Sebastien Bacher |
audacity: statusexplanation |
Could someone please retest this against audacity 1.3 built against wxwidgets2.6 (and GTK2+). I believe it has been fixed by the recent upgrade. |
We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future. |
|