From: Eli Zaretskii <eliz@gnu.org>
To: Ivan Kanis <ivan.kanis@googlemail.com>
Cc: 10582@debbugs.gnu.org
Subject: bug#10582: better backtrace
Date: Sun, 01 Apr 2012 19:19:56 +0300 [thread overview]
Message-ID: <8362djjufn.fsf@gnu.org> (raw)
In-Reply-To: <87k41zybsy.fsf@googlemail.com>
> From: Ivan Kanis <ivan.kanis@googlemail.com>
> Date: Sun, 01 Apr 2012 12:41:01 +0200
>
> Here is the full backtrace including the exception code and the lisp
> backtrace. Let me know what I can do further to identify the problem.
>
> Program received signal SIGPIPE, Broken pipe.
> 0x0012e416 in __kernel_vsyscall ()
>
> #1 0x010a3523 in __write_nocancel () from /lib/libpthread.so.0
> No symbol table info available.
> #2 0x0818e0fc in emacs_write (fildes=10, buf=0xa90b91c "QUIT :\002ERC\002 Version 5.3 (IRC client for Emacs)\r\n", nbyte=48)
> at sysdep.c:1932
> rtnval = 139703669
> bytes_written = 0
> #3 0x08240a3d in send_process (proc=149853781, buf=0xa90b91c "QUIT :\002ERC\002 Version 5.3 (IRC client for Emacs)\r\n",
AFAIK, SIGPIPE means that the other side of the pipe was closed. Is
Emacs communicating with a program or with the network directly? If
the former, please see why does the program exit; if the latter,
perhaps you have connectivity problems?
next prev parent reply other threads:[~2012-04-01 16:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 22:07 bug#10582: 24.0.92; quiting erc causes crash Ivan Kanis
[not found] ` <handler.10582.B.13272700691126.ack@debbugs.gnu.org>
2012-01-26 8:06 ` bug#10582: Acknowledgement (24.0.92; quiting erc causes crash) Ivan Kanis
2012-02-03 18:09 ` Ivan Kanis
2012-03-23 9:03 ` bug#10582: quiting erc causes crash Ivan Kanis
[not found] ` <87398zaduh.fsf_-_@kanis.fr>
2012-03-23 10:08 ` Eli Zaretskii
2012-03-23 14:45 ` Ivan Kanis
2012-03-23 15:36 ` Eli Zaretskii
2012-04-01 10:41 ` bug#10582: better backtrace Ivan Kanis
2012-04-01 16:19 ` Eli Zaretskii [this message]
2012-04-01 16:57 ` Ivan Kanis
2012-04-01 17:02 ` Eli Zaretskii
2012-04-01 20:13 ` Troels Nielsen
2012-04-03 17:58 ` Ivan Kanis
2012-04-27 6:22 ` Ivan Kanis
2012-10-07 1:53 ` Glenn Morris
2012-10-07 9:58 ` Ivan Kanis
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=8362djjufn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10582@debbugs.gnu.org \
--cc=ivan.kanis@googlemail.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).