From: "Kris Warkentin" <kewarken@qnx.com>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>,
"Mark Kettenis" <kettenis@chello.nl>
Subject: Re: found gdbarch solib issue
Date: Tue, 17 Jun 2003 00:40:00 -0000 [thread overview]
Message-ID: <001d01c3346a$798da6d0$2a00a8c0@dash> (raw)
In-Reply-To: <20030616215630.GB12729@nevyn.them.org>
> Shouldn't it be returning arch_info anyway? Why isn't it? Is it
> returning handler->arch_info?
That's what was puzzling me. I was looking through the linked list of 10
million mips arches and thinking what the odds were of compatible ever
equalling the handler arch_info. Seems to me that the return value might be
useful in some circumstances but in this case it should be a boolean, "am I
compatible or not?"
> > - compatible = arch_info->compatible (arch_info,
handler->arch_info);
> > - if (compatible == handler->arch_info)
> > + if(arch_info->compatible (arch_info, handler->arch_info))
cheers,
Kris
prev parent reply other threads:[~2003-06-17 0:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 20:42 Kris Warkentin
2003-06-16 21:57 ` Daniel Jacobowitz
2003-06-17 0:40 ` Kris Warkentin [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='001d01c3346a$798da6d0$2a00a8c0@dash' \
--to=kewarken@qnx.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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