[linedit-devel] maybe a possible bug?

[james morris]

Hi Nikodemus,


I tried getting a backtrace, but C-c does not work. Attached GDB ok, but
there appeared to be no debugging symbols for wherever it was stuck:

----------------------------------------------------
Reading symbols from /usr/bin/sbcl...(no debugging symbols found)...done.
Reading symbols from /lib/libdl.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libpthread.so.0...
(no debugging symbols found)...done.
[Thread debugging using libthread_db enabled]
[New Thread 0x7ff846da06e0 (LWP 3465)]
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libc.so.6...
(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux-x86-64.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from
/var/cache/common-lisp-controller/1000/sbcl/local/home/james/.sbcl/site/osicat_0.5.0/osicat-glue.so...done.
Loaded symbols for
/var/cache/common-lisp-controller/1000/sbcl/local/home/james/.sbcl/site/osicat_0.5.0/osicat-glue.so
Reading symbols from
/var/cache/common-lisp-controller/1000/sbcl/local/home/james/.sbcl/site/linedit_0.16.1/terminal_glue.so...done.
Loaded symbols for
/var/cache/common-lisp-controller/1000/sbcl/local/home/james/.sbcl/site/linedit_0.16.1/terminal_glue.so
Reading symbols from
/var/cache/common-lisp-controller/1000/sbcl/local/home/james/.sbcl/site/linedit_0.16.1/signals.so...done.
Loaded symbols for
/var/cache/common-lisp-controller/1000/sbcl/local/home/james/.sbcl/site/linedit_0.16.1/signals.so

0x00007ff84626fc93 in select () from /lib/libc.so.6
(gdb) step
Cannot find bounds of current function
(gdb) finish
Run till exit from #0  0x00007ff84626fc93 in select () from /lib/libc.so.6
----------------------------------------------------

it hangs again. i go back to terminal running sbcl press a key and:

Warning:
Cannot insert breakpoint 0.
Error accessing memory address 0x0: Input/output error.





anyway i've discovered it's not just ctrl-left/right/up/down but shift
and alt too.

incidently, on x86 laptop the home/end keys work fine but not on amd64.

..

I'm starting get the feeling i'm going to have to learn emacs :/

cheers,
james.





On 1/6/2009, "Nikodemus Siivola" <nikodemus at random-state.net> wrote:

>2009/6/1 james morris <james at jwm-art.net>:
>
>> No problem. I'm still wondering though as to why CTRL-left/right/up/down
>> cause sbcl/linedit to hang? Sorry, i'm only a humble beginner to common
>> lisp so all i can do is report problems :|
>
>No idea, sorry, and I can't even easily reproduce this on my system as
>C-arrows are caught by my window manager -- I'll need to reconfigure
>it before I can have a look.
>
>Once it hangs, can you get a backtrace? Either by C-c at the terminal,
>and typing "ba" <enter> in the debugger (without quotes), or by
>attaching GDB: gdb -p <pid of sbcl>, followed by "ba" <enter> (again
>without quotes) in gdb, followed by "call backtrace_from_fp($rbp,
>100)" (still no quotes)?
>
>Apropos, I hope you are not using Linedit as your _primary_ Lisp
>environment? It is definitely something of a fallback: you are going
>to be a gazillion times more productive using eg. Slime.
>
>> I've attempted to change the key mappings to use home/end keys for
>> bol/eol but came stuck... i know that the keycodes generated for
>> home/end etc are a two-code thing, but not sure how to specify it in the
>> keys file within linedit - the defcommand using "home" and "end"
>> seems to be ignored by these keys which get caught (on my system
>> atleast) by the defcommand for "M-O" (IIRC) and the 2nd part of their
>> keycodes comes out as 'F' or 'H' (IIRC) at the prompt.
>
>Not sure about the cause at all -- it's been a long while since I had
>to figure stuff like that out -- but one thing you can do:
>
>* Trace LINEDIT::READ-CHORD to see what your Home and End keys are
>translated into, if anything.
>
>* If they don't get reasonable translations, add the appropriate
>translations to terminal-translations.lisp.
>
>The whole way terminal stuff is translated is a bit hacky -- the
>proper way would be to try to find the stuff from terminfo db, I
>think.
>
>Cheers,
>
> -- Nikodemus
>
>_______________________________________________
>linedit-devel mailing list
>linedit-devel at common-lisp.net
>http://common-lisp.net/cgi-bin/mailman/listinfo/linedit-devel
>
>