public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlo at alinoe dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/311] dlclose doesn't close all dependent libraries
Date: Tue, 17 Aug 2004 14:19:00 -0000	[thread overview]
Message-ID: <20040817141951.32396.qmail@sourceware.org> (raw)
In-Reply-To: <20040807212132.311.carlo@alinoe.com>


------- Additional Comments From carlo at alinoe dot com  2004-08-17 14:19 -------
Sorry it took so long.

Using LD_DEBUG=all crashed the application, here:

(gdb) bt
#0  0x400115d3 in strlen () from /lib/ld-linux.so.2
#1  0x4000c832 in _dl_debug_vdprintf () from /lib/ld-linux.so.2
#2  0x4000c4c9 in _dl_debug_printf () from /lib/ld-linux.so.2
#3  0x4000bac3 in _dl_signal_cerror () from /lib/ld-linux.so.2
#4  0x40008323 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2
#5  0x4058bffc in do_dlsym () from /lib/tls/libc.so.6
#6  0x00000000 in ?? ()

Not very useful I guess.

I then started to use my libc with debugging symbols, but
that just worked: no crash.

Anyway - I do not understand how to interpret the output.
Some libraries that are loaded and not unloaded aren't even mentioned
in the output.

Can you have a look at the output?  The same libraries
as in the initial report are valid - except that now I am using
g++ 3.5 (20040813), so the path of many libs has changed to
/usr/src/install/3.5.0-20040813/ etc.

The output was bzip2-ed and attached as debug.out.bz2.
dlclosing of the "gui" happens at the [...] between the lines

PLUGIN    : Entering PluginsManager::unload_plugins... <unfinished>
PLUGIN    :     Calling PluginFile::dlclose for plugin "gui".
[...]
PLUGIN    : <continued> leaving.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW


http://sources.redhat.com/bugzilla/show_bug.cgi?id=311

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2004-08-17 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-07 21:21 [Bug libc/311] New: " carlo at alinoe dot com
2004-08-09  8:26 ` [Bug libc/311] " jakub at redhat dot com
2004-08-17 14:16 ` carlo at alinoe dot com
2004-08-17 14:19 ` carlo at alinoe dot com [this message]
2005-07-08 16:26 ` drepper at redhat dot com

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=20040817141951.32396.qmail@sourceware.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@sources.redhat.com \
    /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).