From: Eli Zaretskii <eliz@gnu.org>
To: "andrés ramírez" <rrandresf@gmail.com>
Cc: 28181@debbugs.gnu.org
Subject: bug#28181: 26.0.50; emacs master segfaults on make-network-process, embedded device nokia n900
Date: Thu, 24 Aug 2017 21:24:34 +0300 [thread overview]
Message-ID: <838ti8963h.fsf@gnu.org> (raw)
In-Reply-To: <87valcameb.fsf@chulpaca> (message from andrés ramírez on Thu, 24 Aug 2017 11:47:08 -0600)
> From: andrés ramírez <rrandresf@gmail.com>
> Cc: 28181@debbugs.gnu.org
> Date: Thu, 24 Aug 2017 11:47:08 -0600
>
> > So this indeed looks like some libc problem, and therefore I don't
> > think it's a problem in Emacs.
> I am going to try to find the commit that causes the issue. That could
> help making a workaround, but probably just for this embedded
> device. Could It be a good idea?
I'm almost sure that the problem is with getaddrinfo_a, which we now
use on platforms that provide this function. Maybe you could tweak
the build to not define HAVE_GETADDRINFO_A, and see if that makes the
problem go away.
next prev parent reply other threads:[~2017-08-24 18:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 1:00 bug#28181: 26.0.50; emacs master segfaults on make-network-process, embedded device nokia n900 rrandresf
2017-08-22 14:58 ` Eli Zaretskii
2017-08-22 19:21 ` andrés ramírez
2017-08-23 2:28 ` Eli Zaretskii
2017-08-22 20:08 ` andrés ramírez
2017-08-23 2:32 ` Eli Zaretskii
2017-08-23 3:55 ` andrés ramírez
2017-08-23 17:20 ` Eli Zaretskii
2017-08-23 17:38 ` andrés ramírez
2017-08-23 18:11 ` Eli Zaretskii
2017-08-23 18:46 ` andrés ramírez
2017-08-23 19:06 ` Eli Zaretskii
2017-08-23 19:11 ` andrés ramírez
2017-08-24 2:32 ` Eli Zaretskii
2017-08-24 2:59 ` andrés ramírez
2017-08-24 16:32 ` Eli Zaretskii
2017-08-24 16:44 ` andrés ramírez
2017-08-24 17:38 ` Eli Zaretskii
2017-08-24 17:47 ` andrés ramírez
2017-08-24 18:24 ` Eli Zaretskii [this message]
2017-08-24 19:11 ` andrés ramírez
2017-08-24 19:24 ` Eli Zaretskii
2017-08-24 19:45 ` andrés ramírez
2017-08-25 6:25 ` Eli Zaretskii
2017-08-25 13:10 ` andrés ramírez
2017-08-25 13:21 ` Eli Zaretskii
2017-08-24 21:44 ` andrés ramírez
2017-08-25 6:30 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838ti8963h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28181@debbugs.gnu.org \
--cc=rrandresf@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).