I needed some time to reproduce this. Here is the
traceback (needed help on gdb :-)
(gdb) bt
#0 0x0059c7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x0033a6f1 in connect () from /lib/tls/libpthread.so.0
#2 0x005bedcb in Gpm_Open () from /usr/lib/libgpm.so.1
#3 0x080c241f in
Jean-Yves Levesque jean.yves.leves...@gmail.com writes:
I used gdb to stop the process when it happended
again. The break is in the following function:
_dl_sysinfo_int80
With Linux on i386, int 0x80 is a way to make a system call.
The _dl_sysinfo_int80 function too appears to be used for
I will try it next time. I forgot to mention I
am on GNU/Linux (RHEL 4).
On 9/22/09, Kalle Olavi Niemitalo k...@iki.fi wrote:
Jean-Yves Levesque jean.yves.leves...@gmail.com writes:
It is as if something within elinks is
either looking for a display that does not exist
or for a temporary
On 9/20/09, Kalle Olavi Niemitalo k...@iki.fi wrote:
Jean-Yves Levesque jean.yves.leves...@gmail.com writes:
I do not know if anybody has the same issue as I do
sometimes. When I run elinks within Screen and then
for whatever reason Elinks does not exit cleanly
(Ctrl-C, or crash), If I run
Jean-Yves Levesque jean.yves.leves...@gmail.com writes:
It is as if something within elinks is
either looking for a display that does not exist
or for a temporary file that does not exist either.
That reminds me of commit 5d4beadc4b76f826f006fa951af4b24add12d4f6
(Don't retry get_window_title)
Jean-Yves Levesque jean.yves.leves...@gmail.com writes:
I do not know if anybody has the same issue as I do
sometimes. When I run elinks within Screen and then
for whatever reason Elinks does not exit cleanly
(Ctrl-C, or crash), If I run Elinks again from within Screen, Elinks
seems to hang.
Hello,
On Thu, Sep 17, 2009 at 08:39:08AM +1800, Jean-Yves Levesque wrote:
I do not know if anybody has the same issue as I do
sometimes. When I run elinks within Screen and then
for whatever reason Elinks does not exit cleanly
(Ctrl-C, or crash), If I run Elinks again from within Screen,
