all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 05:32:09 +0300	[thread overview]
Message-ID: <83tw0x8zme.fsf@gnu.org> (raw)
In-Reply-To: <87efs2aykv.fsf@chulpaca> (message from andrés ramírez on Wed, 23 Aug 2017 13:11:44 -0600)

> From: andrés ramírez <rrandresf@gmail.com>
> Cc: 28181@debbugs.gnu.org
> Date: Wed, 23 Aug 2017 13:11:44 -0600
> 
> > > Thread 1 (LWP 11065):
> > > #0  0x001f9874 in mark_compiled (ptr=0x8f75f0) at ../../src/alloc.c:6205
> > > #1  0x001fa1c0 in mark_object (arg=9401845) at ../../src/alloc.c:6478
> > > #2  0x001fa41c in mark_object (arg=1662512) at ../../src/alloc.c:6576
> > 
> > Stack overflow?  How much runtime stack do you have on that system?
> How Should I know that?

ulimit, if you have it there.

> remember emacs-25.2 works

Doesn't necessarily mean anything.

In any case, the backtrace shows the problem didn't happen in
process.c.

Can you show exactly what GDB says at the moment of crash?  I'd like
to see the full text of the message about the fatal signal.





  reply	other threads:[~2017-08-24  2:32 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 [this message]
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=83tw0x8zme.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 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.