Pedro Villavicencio Tue, 18 May 2010 15:16:30 -0000 > Please try to obtain a backtrace of the freeze following the instructions at
> http://wiki.ubuntu.com/DebuggingProgramCrash > and upload the backtrace (as an attachment) to the bug report. Unfortunately I was unable to make a backtrace, as the problem also affects the terminal in which `gdb` is running. How to work around or do correctly? Here's what I did: 0 Attempted to install gnome-terminal debug symbols per instructions @ https://wiki.ubuntu.com/DebuggingProgramCrash m...@local:~$ sudo aptitude update m...@local:~$ apt-cache policy gnome-terminal > gnome-terminal: > Installed: 2.28.1-0ubuntu1 > Candidate: 2.28.1-0ubuntu1 > Version table: > *** 2.28.1-0ubuntu1 0 > 500 http://archive.linux.duke.edu karmic/main Packages > 100 /var/lib/dpkg/status m...@local:~$ sudo aptitude install gnome-terminal-dbgsym=2.28.1-0ubuntu1 ... > The following NEW packages will be installed: > gnome-terminal-dbgsym ... m...@local:~$ sudo aptitude install gdb ... > No packages will be installed, upgraded, or removed. ... However, note "(no debugging symbols found)" below. Following steps are adapted from instructions @ https://wiki.ubuntu.com/Backtrace 1 Restart local (my local machine running ubuntu karmic). Wait for Network Manager to attach to my usual wireless network. Wait for startup terminal to open. Restart emacs (in which I am logging progress). 2 In startup terminal: m...@local:~$ gdb gnome-terminal 2>&1 | tee ${HOME}/gdb-gnome-terminal.txt > GNU gdb (GDB) 7.0-ubuntu > Copyright (C) 2009 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from /usr/bin/gnome-terminal...Reading symbols from > /usr/lib/debug/usr/bin/gnome-terminal...done. > (no debugging symbols found)...done. > (gdb) handle SIG33 pass nostop noprint > Signal Stop Print Pass to program Description > SIG33 No No Yes Real-time event 33 > (gdb) set pagination 0 > (gdb) run > Starting program: /usr/bin/gnome-terminal > [Thread debugging using libthread_db enabled] Note new terminal starts. 3 In panel, click Network Manager>VPN Connections>the VPN, and login to the VPN. 4 In the new terminal: m...@local:~$ date ; ssh -Y [email protected] > Tue May 18 18:29:24 EDT 2010 ... > [email protected]'s password: Note successful login. 5 After ssh connection, click Network Manager>VPN Connections>Disconnect VPN 6 Verify that new terminal is hung, e.g. does not respond to keyboard. 7 In gdb terminal, hit C-c. I then attempt to do (gdb) backtrace full (gdb) info registers (gdb) x/16i $pc (gdb) thread apply all backtrace (gdb) quit but the gdb terminal is also hung :-( So there seem to be 2 problems: 0 no debugging symbols found for gnome-terminal 1 the terminal running `gdb` also hangs, preventing getting the backtrace How to fix or workaround? -- failure of ssh-over-VPN connection hangs terminal https://bugs.launchpad.net/bugs/581937 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
