Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org, 140494-done@bugs.debian.org
Subject: Re: [parisc-linux] dynamic loader problem
Date: Sat, 6 Apr 2002 09:54:52 -0800	[thread overview]
Message-ID: <20020406175452.GF356@tausq.org> (raw)
In-Reply-To: <200203111808.g2BI8u5N013881@hiauly1.hia.nrc.ca>

In reference to a message from John David Anglin, dated Mar 11:
> In looking at the the failure of the g++.brendan/new3.C, I have observed
> what appears to be a problem with the dynamic loader.  The function
> _Znwj appears as a global symbol in the main program and in
> libstdc++.so.4.0.0.  The version in the main program should be selected
> in preference to the one in the shared library.  However, the dynamic
> loader actually uses the version in the shared library causing the
> test to fail.  The program works ok with static linkage.
> 
> It looks like the symbol search procedure used in glibc needs some work.

ok, recently events have prompted me to look at this again...

isn't the test itself broken?

it does this:

void *operator new(size_t sz) .....

int main() 
{
  A *bb = new A[10]; 
  ...
}

you define "operator new", but are calling operator new[], so it
defaults to the one in libstdc++...

if you change the definition of "operator new" to "operator new[]" then
the test will pass.

randolph
-- 
   @..@                                         http://www.TauSq.org/
  (----)
 ( >__< )
 ^^ ~~ ^^

  parent reply	other threads:[~2002-04-06 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-11 18:08 [parisc-linux] dynamic loader problem John David Anglin
2002-03-12  6:01 ` Randolph Chung
2002-03-12 16:08   ` John David Anglin
2002-03-12 16:46     ` Randolph Chung
2002-04-06 17:54 ` Randolph Chung [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-12 17:08 Thibaut VARENE

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=20020406175452.GF356@tausq.org \
    --to=randolph@tausq.org \
    --cc=140494-done@bugs.debian.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@lists.parisc-linux.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