From: Reinaldo Molina <me@molinamail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Martin Simmons <qqxnjvamvxwx@dyxyl.com>, gdb@sourceware.org
Subject: Re: gdb refuses to connect to localhost
Date: Tue, 29 Dec 2020 20:20:23 -0500 [thread overview]
Message-ID: <20201230012023.yehrsfvjigjhwmne@molinamail.com> (raw)
In-Reply-To: <18d87f2e-31d3-529d-3433-31593089eccf@polymtl.ca>
> Is it maybe an instance of this bug?
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=26116
Initially I thought so. I have a fancy prompt. But then I was able to
reproduce it even in bash. I went for the prompts then, but still could
reproduce. Then I went for something I should have done a while back,
but didn't occur to me:
env -i gdbserver localhost:8888 build/bin/nvim
And it functions properly that way.
So that seems to indicate that is related to my environment variables. I
have only a few in my `bashrc` and I can still reproduce, so tomorrow
I'll debug it. See what I can find.
Thanks,
Reinaldo Molina
On 12-29-20 16:18:21, Simon Marchi wrote:
>
>
> On 2020-12-29 10:58 a.m., Reinaldo Molina via Gdb wrote:
> > That did it!!!
> >
> > My shell is `zsh` by the way.
> >
> > > zsh --version
> > zsh 5.8 (x86_64-pc-linux-gnu)
> >
> > Thank you guys! Happy New Year!
> >
> > Reinaldo Molina
>
> Wow, good job at spotting this Martin.
>
> Is it maybe an instance of this bug?
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=26116
>
> Simon
prev parent reply other threads:[~2020-12-30 1:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 22:36 Reinaldo Molina
2020-12-25 22:55 ` Simon Marchi
2020-12-25 23:45 ` Reinaldo Molina
2020-12-26 0:00 ` Simon Marchi
2020-12-28 15:56 ` Reinaldo Molina
2020-12-28 22:29 ` Simon Marchi
2020-12-25 23:04 ` Andreas Schwab
2020-12-26 0:00 ` Reinaldo Molina
2020-12-29 15:48 ` Martin Simmons
2020-12-29 15:58 ` Reinaldo Molina
2020-12-29 21:18 ` Simon Marchi
2020-12-30 1:20 ` Reinaldo Molina [this message]
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=20201230012023.yehrsfvjigjhwmne@molinamail.com \
--to=me@molinamail.com \
--cc=gdb@sourceware.org \
--cc=qqxnjvamvxwx@dyxyl.com \
--cc=simon.marchi@polymtl.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).