From: "andrés ramírez" <rrandresf@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28181@debbugs.gnu.org
Subject: bug#28181: 26.0.50; emacs master segfaults on make-network-process, embedded device nokia n900
Date: Wed, 23 Aug 2017 11:38:25 -0600 [thread overview]
Message-ID: <87h8wyb2we.fsf@chulpaca> (raw)
In-Reply-To: <838tia9p5x.fsf@gnu.org>
> Then how do you know the problem was in process.c? The backtrace
> you've shown stops before it gets to Emacs sources. Maybe try "thread
> apply all bt" instead of just "bt", you may have shown backtrace for a
> non-main thread.
I edebbugged it. then gdbbed it
started from the eww function
url-retrieve
url-retrieve-internal
url-http
[...]
make-network-process (i put a breakpoint there too)
when entering make-network-process the segfault happened.
next prev parent reply other threads:[~2017-08-23 17:38 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8wyb2we.fsf@chulpaca \
--to=rrandresf@gmail.com \
--cc=28181@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.