Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] [new testcase] Regression on qsort_cmp [Re: status of  	Darwin support]
Date: Tue, 25 Aug 2009 17:51:00 -0000	[thread overview]
Message-ID: <8ac60eac0908251020w721af576tc18830a09449ea3c@mail.gmail.com> (raw)
In-Reply-To: <20090825084723.GA24462@host0.dyn.jankratochvil.net>

On Tue, Aug 25, 2009 at 1:47 AM, Jan
Kratochvil<jan.kratochvil@redhat.com> wrote:

> Requesting approval for the testcase check-in.
> Tested on {x86_64,i686}-fedorarawhide-linux-gnu:
> FAIL: gdb.base/solib-overlap.exp: 0x40000000: attach (GDB internal error)
> FAIL: gdb.base/solib-overlap.exp: 0x50000000: attach (GDB internal error)

Thanks for the test. It nicely reproduces the problem, and is fixed by the
"remove assertions and deal with possible unexpected overlaps" patch I am
working on :)

I do have a general question on testing shlibs though:

In order to run this test on x86_64, I had to do this:

-    set lib_flags {debug}
+    set lib_flags {debug additional_flags=-fpic}

Otherwise, I get
  gdb.base/solib-overlap-lib.c.o: relocation R_X86_64_32 against `a
local symbol' can not be used when making a shared object; recompile
with -fPIC
and the test goes UNTESTED.

Shouldn't gdb_compile_shlib be adding '-fpic' automatically?
Or is the above correct fix for that test?

Thanks,
-- 
Paul Pluzhnikov


  reply	other threads:[~2009-08-25 17:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3bpmvfro1.fsf@fleche.redhat.com>
     [not found] ` <200908041804.30240.thiago.bauermann@gmail.com>
     [not found]   ` <20090805044504.GJ4370@adacore.com>
     [not found]     ` <4A7ABAF0.7010004@Sun.COM>
     [not found]       ` <C11EE4DE-A0A0-4A9E-A86E-9153A7AC81C8@adacore.com>
     [not found]         ` <4A7FFAB3.7080903@Sun.COM>
     [not found]           ` <m33a7z8qq5.fsf@fleche.redhat.com>
     [not found]             ` <8ac60eac0908101320k6cc20e9age92656cba254a5d4@mail.gmail.com>
     [not found]               ` <4A812B8B.8040202@Sun.COM>
     [not found]                 ` <20090825084613.GA22242@host0.dyn.jankratochvil.net>
2009-08-25  9:40                   ` Jan Kratochvil
2009-08-25 17:51                     ` Paul Pluzhnikov [this message]
2009-08-25 19:15                       ` [patch] [new testcase] Regression on qsort_cmp Jan Kratochvil
2009-08-31 22:56                         ` Tom Tromey
2009-09-01 12:08                           ` Jan Kratochvil

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=8ac60eac0908251020w721af576tc18830a09449ea3c@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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