From: Onno Kortmann <onno@gmx.net>
To: sid@sourceware.org, "Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: Bugreport: Latest CVS checkout of sid: segfault with empty file w/o configuration(?)
Date: Fri, 31 Mar 2006 20:10:00 -0000 [thread overview]
Message-ID: <200603312210.16824.onno@gmx.net> (raw)
In-Reply-To: <20060331184053.GC22505@redhat.com>
Hi,
> > [...] I tried to run a sid with the following on-line input file:
> > load libmemory.la mem_component_library
> > But sid segfaults. [...]
>
> Of course that shouldn't happen (and doesn't in my build). You can
> sic a debugger on the binary, and see what's up at the point of crash.
Ok, sorry, my bug report was a bit short, I just thought that I broke it by
entering a very weird configuration :)
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()); <--------
The lt_dlopen segfaults when opening the memory component. For the
configuration component, lt_dlopen(..) returns zero and the following peek
into the sid executable itself succeeds.
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. I changed lt_dlopen to lt_dlopenext in this line, I changed the library
in the configuration file to ".a", ".la", ".so" and even set the full path in
the configuration file - didn't help either.
Replacing ltdl.c in component/cfgroot/... with a newer one from the debian
archive (apt-get source libltdl, version 1.5.22) still segfaults.
My system is running kernel 2.6.12/i686 on Debian testing. Libc:
$ /lib/libc.so.6
GNU C Library stable release version 2.3.5, by Roland McGrath et al.
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.0.3 20051023 (prerelease) (Debian 4.0.2-3).
Compiled on a Linux 2.6.13 system on 2005-11-13.
Available extensions:
GNU libio by Per Bothner
crypt add-on version 2.1 by Michael Glad and others
GNU Libidn by Simon Josefsson
linuxthreads-0.10 by Xavier Leroy
BIND-8.2.3-T5B
libthread_db work sponsored by Alpha Processor Inc
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Thread-local storage support included.
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.
I installed sid systemwide by doing a make install in a checkout of your CVS,
in the subdirectory src/sid.
Best regards,
Onno
next prev parent reply other threads:[~2006-03-31 20:10 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 [this message]
2006-04-06 14:34 ` Frank Ch. Eigler
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=200603312210.16824.onno@gmx.net \
--to=onno@gmx.net \
--cc=fche@redhat.com \
--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).