From: mancha1@hush.com
To: gdb@sourceware.org
Subject: GDB unable to trace xchat on linux
Date: Tue, 16 Apr 2013 14:55:00 -0000 [thread overview]
Message-ID: <20130416145501.6D4AFE6736@smtp.hushmail.com> (raw)
Hello.
I am using GDB 7.5.1 and trying to trace xchat 2.8.8 compiled with
-ggdb and default configure options (see below).
To reproduce:
$ gdb /path/to/xchat
(gdb) r
xchat starts but hangs at "Looking up <insert server used here>".
xchat's faq (http://xchat.org/gdb/) suggests GDB has trouble debugging
when a server hostname is used. As they suggest, I ran a local ircd and
used 127.0.0.1. The problem remains.
Any linux GDB gurus out there that can offer some guidance on what the
problem is?
--mancha
PS. When in this hung state, ^C followed by "thread apply all bt" gives
the following stack. Also after SIGINT and quit from GDB in this state,
xchat's window stays open and the process is unkillable. ps x shows it
in state "t".
#0 0xb7fde424 in __kernel_vsyscall ()
#1 0xb7eed8bb in poll () from /lib/libc.so.6
#2 0xb6e481e6 in g_poll () from /usr/lib/libglib-2.0.so.0
#3 0xb6e3a3ad in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#4 0xb6e3aaef in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#5 0xb7b29fcb in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#6 0x08060da2 in fe_main () at fe-gtk.c:290
#7 0x080b4904 in main (argc=1, argv=0xbfffef14) at xchat.c:920
PPS. Default configuration on this system:
xchat 2.8.8
Building GTK+ Interface .... : yes
Building TEXT Interface .... : no
PLUGINS: Perl: yes Python: yes TCL: yes
mmx tinting ......... : yes spelling .............. : libsexy
XShm tinting ........ : no plugin interface ...... : yes
text backend ........ : pango nls/gettext ........... : yes
openssl support ..... : yes ipv6 support .......... : no
dbus support ........ : yes msproxy ntlm (ISA) .... : no
next reply other threads:[~2013-04-16 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 14:55 mancha1 [this message]
2013-04-16 22:08 ` Sergio Durigan Junior
2013-04-16 23:10 mancha1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130416145501.6D4AFE6736@smtp.hushmail.com \
--to=mancha1@hush.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox