rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Tom Culliton <culliton@clark.net>
To: Paul Haahr <haahr@netcom.com>
Cc: Tom Culliton <culliton@clark.net>,
	Russell Davies <c9415019@cs.newcastle.edu.au>,
	rc@hawkwind.utcs.toronto.edu, culliton@clark.net
Subject: Re: rc,linux,signal,readline
Date: Tue, 12 Aug 1997 17:55:46 -0400	[thread overview]
Message-ID: <199708122155.RAA15689@clark.net> (raw)
In-Reply-To: Your message of "Tue, 12 Aug 1997 14:24:34 PDT." <8PZdii2+2@localhost.localdomain.netcom.com>

On Tue, 12 Aug 1997 14:24:34 PDT, Paul Haahr wrote:
> > >  	I have been trying for a while now to get the following 
> > >  	working under linux..without success..
> > >  
> > >  	a _dynamically linked_ rc shell with;
> > 
> > I have sent patches to the list which take care of all the rest of
> > your requests, but for some reason the shared/dynamic version of GNU
> > readline doesn't work like the static version.  At least thats my
> > first guess as to the problem.  Without readline it works "properly"
> > and trips clean when linked dynamically.  With readline it doesn't.
> 
> Could it be that you're getting the wrong readline.so?  There were real
> changes between the 1.x and 2.x versions, as I remember.

Not as far as I could tell.  There are no rcs ident strings in the
libraries (Hey, Chet!) but the libs are:

-rw-r--r--   1 root     root       154214 Aug 19  1996 /usr/lib/libreadline.a
-rw-r--r--   1 root     root       132113 Aug 19  1996 /usr/lib/libreadline.so.2.0

and look pretty much the same via nm.  I spent quite a bit of time on
this but not being an expert on dynamic linking didn't dig too deep.

BTW - does anyone know why on DEC Alpha OSF1, using the libreadline
from the freeware CD, it dumps core when I hit ^R?  The trace back
looks like this:

(gdb) core core
Core was generated by `rc'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/shlib/libc.so...done.
#0  0x3ff800d1870 in strlen ()
(gdb) where
#0  0x3ff800d1870 in strlen ()
#1  0x3ff800d94f0 in _doprnt ()
#2  0x3ff800d5538 in sprintf ()
#3  0x120034da4 in rl_message (format=0x14000a830 "%s", arg1=1073818992,
    arg2=0) at display.c:669
#4  0x120035a20 in rl_display_search (search_string=0x140015d00 "",
    reverse_p=1, where=-1) at isearch.c:106
#5  0x120035c8c in rl_search_history (direction=-1, invoking_key=18)
    at isearch.c:193
#6  0x1200358a0 in rl_reverse_search_history (sign=1, key=18) at isearch.c:61
#7  0x120020970 in rl_dispatch (key=18, map=0x140000fb0) at readline.c:636
#8  0x12002007c in readline_internal () at readline.c:345
#9  0x12001fe80 in readline (prompt=0x140012c80 "[culliton@cns5]rc-1.5tjc/ : ")
    at readline.c:268
#10 0x120016f18 in ugchar ()
#11 0x120016fe4 in ugchar ()
warning: Hit heuristic-fence-post without finding
warning: enclosing function for address 0xa79d9180f43ffffd
This warning occurs if you are debugging a function without any symbols
(for example, in a stripped executable).  In that case, you may wish to
increase the size of the search with the `set heuristic-fence-post' command.

Otherwise, you told GDB there was a function where there isn't one, or
(more likely) you have encountered a bug in GDB.


Pretty cool, huh? ;-)


  reply	other threads:[~1997-08-12 22:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-12  8:19 rc,linux,signal,readline Russell Davies
1997-08-12  9:42 ` rc,linux,signal,readline Tim Goodwin
1997-08-12 13:59 ` rc,linux,signal,readline Tom Culliton
1997-08-12 21:24   ` rc,linux,signal,readline Paul Haahr
1997-08-12 21:55     ` Tom Culliton [this message]
1997-08-13 13:33       ` rc,linux,signal,readline Tim Goodwin
1997-08-13 14:20         ` rc,linux,signal,readline Tom Culliton
1997-08-13 17:57         ` rc,linux,signal,readline Tom Culliton

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199708122155.RAA15689@clark.net \
    --to=culliton@clark.net \
    --cc=c9415019@cs.newcastle.edu.au \
    --cc=haahr@netcom.com \
    --cc=rc@hawkwind.utcs.toronto.edu \
    /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.
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 NNTP newsgroup(s).