From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Christian Thalinger <Christian.Thalinger@sun.com>
Cc: Tom Tromey <tromey@redhat.com>,
Tristan Gingold <gingold@adacore.com>,
Joel Brobecker <brobecker@adacore.com>,
Thiago Jung Bauermann <thiago.bauermann@gmail.com>,
gdb@sourceware.org
Subject: Re: status of Darwin support
Date: Tue, 11 Aug 2009 16:33:00 -0000 [thread overview]
Message-ID: <8ac60eac0908110933s6caf5abdsa1320f626dea860b@mail.gmail.com> (raw)
In-Reply-To: <4A812B8B.8040202@Sun.COM>
On Tue, Aug 11, 2009 at 1:27 AM, Christian Thalinger
<Christian.Thalinger@sun.com> wrote:
> The assert you removed was at line 801, but my assert is at 792. And,
> obviously, it still asserts. These are the values:
Indeed, this is a different assert from the one that fired on Linux,
sorry I missed that.
> (gdb) r
> Starting program:
> /Users/twisti/bsd-port/hotspot/build/bsd/bsd_i486_compiler2/jvmg/gamma
I assume these are from debug prints of (section addr? or endaddr?) you've
added? They look like possibly non-relocated section addresses.
> 0x4fd3 <= 0x7040
> 0x70d1 <= 0xc9b7
> 0x5ffd <= 0x7040
> 0x6015 <= 0x7040
> 0x6034 <= 0x7040
> 0x6074 <= 0x7040
> 0x7014 <= 0x7040
> 0x4fd3 <= 0x7040
> 0x4fd3 <= 0x7040
> 0x6074 <= 0x7040
> 0x6015 <= 0x7040
> 0x6eee <= 0x7040
> 0x5ffd <= 0x6000
> 0x6015 <= 0x6018
> 0x6034 <= 0x6034
> 0x6074 <= 0x7000
> 0x4fd3 <= 0x1bc2
> objfiles.c:793: internal-error: qsort_cmp: Assertion
> `obj_section_endaddr (sect1) <= sect2_addr' failed.
>
> I'm not sure that helps...
Could you run gdb under /usr/bin/gdb, like this:
/usr/bin/gdb --args ./gdb -nx
/Users/twisti/bsd-port/hotspot/build/bsd/bsd_i486_compiler2/jvmg/gamma
(top-gdb) break error
(top-gdb) run
(gdb) run
### You may hit error several times before the 'qsort_cmp' fires.
### Once it does, go up to qsort_cmp level and (at the (top-gdb) prompt):
print *sect1->the_bfd_section
print *sect1->objfile
print *sect2->the_bfd_section
print *sect2->objfile
Thanks,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-08-11 16:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 20:29 Christian Thalinger
2009-08-04 16:52 ` Tom Tromey
2009-08-04 21:03 ` Thiago Jung Bauermann
2009-08-05 4:45 ` Joel Brobecker
2009-08-06 11:14 ` Christian Thalinger
2009-08-06 11:17 ` Jonas Maebe
2009-08-10 9:41 ` Tristan Gingold
2009-08-10 10:47 ` Christian Thalinger
2009-08-10 18:36 ` Tom Tromey
2009-08-10 20:20 ` Paul Pluzhnikov
2009-08-11 5:06 ` Paul Pluzhnikov
2009-08-11 6:59 ` Tristan Gingold
2009-08-11 7:14 ` Paul Pluzhnikov
2009-08-11 7:43 ` Tristan Gingold
2009-08-11 8:20 ` Christian Thalinger
2009-08-11 8:28 ` Christian Thalinger
2009-08-11 16:33 ` Paul Pluzhnikov [this message]
2009-08-11 16:43 ` Christian Thalinger
2009-08-11 16:48 ` Paul Pluzhnikov
2009-08-11 16:49 ` Christian Thalinger
2009-08-11 17:12 ` Paul Pluzhnikov
2009-08-11 17:25 ` Christian Thalinger
2009-08-11 17:38 ` Paul Pluzhnikov
2009-08-11 17:54 ` Christian Thalinger
2009-08-12 16:26 ` Paul Pluzhnikov
2009-08-12 16:45 ` Christian Thalinger
2009-08-26 0:18 ` [patch] [new testcase] Regression on qsort_cmp [Re: status of Darwin support] Jan Kratochvil
2009-09-08 9:31 ` Tristan Gingold
2009-09-08 13:04 ` Jack Howarth
2009-08-06 10:51 ` status of Darwin support Christian Thalinger
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=8ac60eac0908110933s6caf5abdsa1320f626dea860b@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=Christian.Thalinger@sun.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.com \
--cc=thiago.bauermann@gmail.com \
--cc=tromey@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