[elinks-users] Elinks within Screen question

Jean-Yves Levesque jean.yves.levesque at gmail.com
Thu Oct 15 10:53:06 PDT 2009

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 init_mouse (cons=Variable "cons" is not available.
) at unix.c:91
#4  0x080c2439 in handle_mouse (cons=0, fn=0xfffffe00,
data=0xfffffe00) at unix.c:107
#5  0x080ee7cd in enable_mouse () at mouse.c:95
#6  0x080ed1fe in handle_trm (std_in=0, std_out=1, sock_in=9,
sock_out=9, ctl_in=0, init_string=0x9282d10, init_len=0, remote=0) at
#7  0x080b8231 in init () at main.c:235
#8  0x080b8bd7 in select_loop (init=0x80b7eb8 <init>) at select.c:222
#9  0x080b8465 in main (argc=1, argv=0xbff3a6d4) at main.c:358

Also, it does happen outside ot gnu screen so this is not a screen
issue per say.

Any idea?


On 9/26/09, Kalle Olavi Niemitalo <kon at iki.fi> wrote:
> Jean-Yves Levesque <jean.yves.levesque at 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
> several system calls: at least semop, select, and read.
> Can you get a backtrace with the debugger, to see which
> system call it is and whether it's being made by ELinks itself
> or by some library (e.g. libX11)?
> _______________________________________________
> elinks-users mailing list
> elinks-users at linuxfromscratch.org
> http://linuxfromscratch.org/mailman/listinfo/elinks-users

Je ne parle qu'en mon nom.
I am only speaking for myself.

More information about the elinks-users mailing list