From: "Doug Evans" <dje@google.com>
To: gdb@sourceware.org
Subject: Re: sol-thread.c core_ops oddity
Date: Thu, 07 Aug 2008 19:44:00 -0000 [thread overview]
Message-ID: <e394668d0808071244la843350w178a439ab48e6e0a@mail.gmail.com> (raw)
In-Reply-To: <20080807192518.GA31697@caradoc.them.org>
On Thu, Aug 7, 2008 at 12:25 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Thu, Aug 07, 2008 at 12:11:36PM -0700, Doug Evans wrote:
>> Obviously I'm missing something.
>> I don't have a solaris system to see what really happens,
>> can someone fill in the missing piece that makes the above work?
>
> Luck and sorting. I'm pretty sure we generate the calls in
> alphabetical order (by filename or by function, I'm not sure).
Thanks. I don't see any sorting beyond
INIT_FILES = $(COMMON_OBS) $(TSOBS) $(CONFIG_SRCS)
and the hack for gdbtypes.
Is there an intention to officially sanction the sorting as something
one can take advantage of?
I'd like to fix the misleading comments but it's not clear what better
wording should be.
next prev parent reply other threads:[~2008-08-07 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 19:12 Doug Evans
2008-08-07 19:26 ` Daniel Jacobowitz
2008-08-07 19:44 ` Doug Evans [this message]
2008-08-07 19:58 ` Stan Shebs
2008-08-07 20:06 ` Daniel Jacobowitz
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=e394668d0808071244la843350w178a439ab48e6e0a@mail.gmail.com \
--to=dje@google.com \
--cc=gdb@sourceware.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