From: mancha1@hush.com
To: sergiodj@redhat.com
Cc: gdb@sourceware.org
Subject: Re: GDB unable to trace xchat on linux
Date: Tue, 16 Apr 2013 23:10:00 -0000 [thread overview]
Message-ID: <20130416231014.A371A14DBE1@smtp.hushmail.com> (raw)
On Tue, 16 Apr 2013 18:08:34 -0400 "Sergio Durigan Junior"
<sergiodj@redhat.com> wrote:
>On Tuesday, April 16 2013, mancha1@hush.com wrote:
>
>> To reproduce:
>>
>> $ gdb /path/to/xchat
>> (gdb) r
>>
>> xchat starts but hangs at "Looking up <insert server used
>here>".
>
>What do you mean by "hangs"? Is it unresponsible? Can you still
>issue
>commands on it? Is it just waiting for the server to respond?
>
By "hangs" I mean it doesn't progress beyond "Looking up...". I am
still able to navigate the menus and open pop-ups say via "About"
menus, etc. while in this state. However, it becomes totally
unresponsive if I Server->Disconnect or XChat->Quit.
>> 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.
>
>The page doesn't suggest that. It only suggests that you use the
>server's IP address directly. Anyway, have you tried that? You
>could
>try freenode's IP address (84.240.3.129) and see if it works.
>
I understood the FAQ. I ran an ircd locally to speed up my
debugging. No numeric IP works (freenode or otherwise).
To make this crystal clear: no connection progresses beyond the
"looking up..." message: not hostname not IP, not local, not
remote, nor any permutations thereof.
next reply other threads:[~2013-04-16 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 23:10 mancha1 [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-04-16 14:55 mancha1
2013-04-16 22:08 ` Sergio Durigan Junior
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=20130416231014.A371A14DBE1@smtp.hushmail.com \
--to=mancha1@hush.com \
--cc=gdb@sourceware.org \
--cc=sergiodj@redhat.com \
/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