public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: Andreas Schwab <schwab@suse.de>
Cc: libc-hacker@sources.redhat.com
Subject: Re: Crash in DT_FINI_ARRAY
Date: Thu, 23 Jan 2003 19:45:00 -0000	[thread overview]
Message-ID: <15920.18006.383327.719985@napali.hpl.hp.com> (raw)
In-Reply-To: <jer8b4qaij.fsf@sykes.suse.de>

What platform did it crash on?  I'm sure I tested it on ia64 and it
worked fine, there (at least it got through the test-suite without
visible errors).

	--david

>>>>> On Thu, 23 Jan 2003 14:08:20 +0100, Andreas Schwab <schwab@suse.de> said:

  Andreas> The pointers in DT_FINI_ARRAY are already relocated.
  Andreas> Andreas.

  Andreas> 2003-01-23 Andreas Schwab <schwab@suse.de>

  Andreas> 	* elf/dl-close.c (_dl_close): Don't relocate
  Andreas> DT_FINI_ARRAY elements.

  Andreas> --- elf/dl-close.c.~1.93.~ 2003-01-16 11:19:32.000000000
  Andreas> +0100 +++ elf/dl-close.c 2003-01-22 21:11:29.000000000
  Andreas> +0100 @@ -241,7 +241,7 @@ _dl_close (void *_map) unsigned
  Andreas> int cnt;
 
  Andreas>  		  for (cnt = 0; cnt < sz; ++cnt) - ((fini_t)
  Andreas> (imap->l_addr + array[cnt])) (); + ((fini_t) array[cnt])
  Andreas> (); }
 
  Andreas>  	      /* Next try the old-style destructor.  */

  Andreas> -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux AG,
  Andreas> Deutschherrnstr. 15-19, D-90429 Nürnberg Key fingerprint =
  Andreas> 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now
  Andreas> for something completely different."

  reply	other threads:[~2003-01-23 19:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23 13:08 Andreas Schwab
2003-01-23 19:45 ` David Mosberger [this message]
2003-01-23 22:09   ` Andreas Schwab
2003-01-23 22:22     ` David Mosberger
2003-01-24 21:28 ` Andreas Schwab
2003-01-27 20:44   ` Ulrich Drepper

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=15920.18006.383327.719985@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=davidm@hpl.hp.com \
    --cc=libc-hacker@sources.redhat.com \
    --cc=schwab@suse.de \
    /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).