public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Onno Kortmann <onno@gmx.net>
Cc: sid@sourceware.org
Subject: Re: Bugreport: Latest CVS checkout of sid: segfault with empty file w/o configuration(?)
Date: Thu, 06 Apr 2006 14:34:00 -0000	[thread overview]
Message-ID: <20060406143358.GE16498@redhat.com> (raw)
In-Reply-To: <200603312210.16824.onno@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]

Hi -

On Fri, Mar 31, 2006 at 10:10:16PM +0200, Onno Kortmann wrote:
> [...]
> I have now debugged it (somehow the backtrace was of no help, lacked symbols 
> and was messed up - so I got to this location iteratively!) until this line 
> in compConfig.cxx:
> 
> bool
> cfgroot_component::register_dso(const string& dso_name, const string& 
> _symbol_name)
> {
>   lt_dlhandle dl_handle = 0;
> 
>   // Try ordinary dynamic linking
>   dl_handle = lt_dlopen(dso_name.c_str());     <--------

Try recompiling the whole thing with "CFLAGS=-g CXXFLAGS=-g".  It may
help explain why lt_dlopen failed, if perhaps something is wrong with
dso_open.

Another fall-back option is to configure with "--disable-shared",
which will link in component libraries right into the sid binary.


> I installed sid with the default prefix into /usr/local. I added
> /usr/local/sid/sidcomp to the LD_LIBRARY_PATH as a test - this did
> not help. [...]

sid tries to locate its component shared libraries using several
means, including the SID_EXEC_PREFIX environment variable, and the
location of its own executable.  Because of the latter, it should
just work without additional environment settings.

- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-04-06 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 18:10 Onno Kortmann
2006-03-31 18:41 ` Frank Ch. Eigler
2006-03-31 20:10   ` Onno Kortmann
2006-04-06 14:34     ` Frank Ch. Eigler [this message]
2006-04-08  0:14       ` Onno Kortmann

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=20060406143358.GE16498@redhat.com \
    --to=fche@redhat.com \
    --cc=onno@gmx.net \
    --cc=sid@sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).