Open GoogleCodeExporter opened 8 years ago
SIGPIPE shouldn't be the cause of crash.
Could you continue (type c) in gdb? I think the crash occur after that.
Original comment by somsaks
on 22 Jan 2010 at 2:17
here is a better trace:
$ gdb --args pidgin -c .purple_remote/
GNU gdb (GDB) 7.0.1-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/pidgin...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/pidgin -c .purple_remote/
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffe1c84710 (LWP 28478)]
[New Thread 0x7fffd6b42710 (LWP 28520)]
[Thread 0x7fffd6b42710 (LWP 28520) exited]
Program received signal SIGPIPE, Broken pipe.
0x00007ffff798f74d in write () at ../sysdeps/unix/syscall-template.S:82
82 ../sysdeps/unix/syscall-template.S: No such file or directory.
in ../sysdeps/unix/syscall-template.S
Current language: auto
The current source language is "auto; currently asm".
(gdb) c
Continuing.
Program received signal SIGPIPE, Broken pipe.
0x00007ffff798f74d in write () at ../sysdeps/unix/syscall-template.S:82
82 in ../sysdeps/unix/syscall-template.S
(gdb) c
Continuing.
Program received signal SIGPIPE, Broken pipe.
0x00007ffff798f74d in write () at ../sysdeps/unix/syscall-template.S:82
82 in ../sysdeps/unix/syscall-template.S
(gdb) c
Continuing.
Original comment by BUGabu...@gmail.com
on 26 Jan 2010 at 8:45
FYI this happen just on startup, so not exactly as described in the first post
Original comment by BUGabu...@gmail.com
on 26 Jan 2010 at 8:47
Original issue reported on code.google.com by
BUGabu...@gmail.com
on 22 Jan 2010 at 2:13