From: Joel Brobecker <brobecker@adacore.com>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] wrong pointer type length
Date: Thu, 17 May 2007 17:23:00 -0000 [thread overview]
Message-ID: <20070517172334.GC508@adacore.com> (raw)
In-Reply-To: <m3irar8jwj.fsf@codesourcery.com>
> If the assembler is doing this in other cases, you're going to be
> pretty hosed. STABS requires records to appear in the order
> specified.
I know :-(. Unfortunately, we can't change the assembler, so I've added
no too long ago a second list of undefined types that should allow us
to handle this type of wild reordering. See:
http://www.sourceware.org/ml/gdb-patches/2007-02/msg00387.html
--
Joel
prev parent reply other threads:[~2007-05-17 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 16:19 Joel Brobecker
2007-05-17 16:27 ` Daniel Jacobowitz
2007-05-17 16:42 ` Joel Brobecker
2007-05-17 18:51 ` [RFA] wrong pointer type length part 2 (of 2) Joel Brobecker
2007-05-17 20:07 ` Daniel Jacobowitz
2007-05-17 20:16 ` Joel Brobecker
2007-05-17 17:01 ` [RFA] wrong pointer type length Jim Blandy
2007-05-17 17:23 ` Joel Brobecker [this message]
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=20070517172334.GC508@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.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