From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <drow@false.org>,
mark.kettenis@xs4all.nl, gdb-patches@sourceware.org
Subject: Re: [rfc] Clarify shared library warning
Date: Thu, 12 Oct 2006 05:52:00 -0000 [thread overview]
Message-ID: <20061012055231.GG1059@adacore.com> (raw)
In-Reply-To: <u1wpejgxf.fsf@gnu.org>
> This doesn't mention the problem with the library version, which to me
> is a very important clue. I think version mismatch is a much more
> likely problem than a library mismatch.
But two libraries with the exact same version number may not necessarily
be the same. The last time I've had this problem was a few weeks ago
when a customer of ours sent us a core file. Same system version number
(HP/UX), same shared library version number, and yet different code.
That's why I think it's important to say "wrong shared library".
I actually read "version" in the original proposal as "instance" more
than "number". Isn't that interesting?
In any case, I agree with Mark that an addition to the manual is
more important than trying to cover every possible sources for this
discrepency in a highly skilfully crafted short message. I am very
happy with the warning, no matter how it tries to say it.
--
Joel
next prev parent reply other threads:[~2006-10-12 5:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 14:52 Daniel Jacobowitz
2006-10-10 21:28 ` Eli Zaretskii
2006-10-10 21:34 ` Joel Brobecker
2006-10-11 13:38 ` Daniel Jacobowitz
2006-10-11 16:09 ` Joel Brobecker
2006-10-11 20:32 ` Mark Kettenis
2006-10-11 20:39 ` Daniel Jacobowitz
2006-10-11 20:49 ` Mark Kettenis
2006-10-11 20:51 ` Daniel Jacobowitz
2006-10-12 4:29 ` Eli Zaretskii
2006-10-12 5:52 ` Joel Brobecker [this message]
2006-10-12 6:55 ` Eli Zaretskii
2006-10-12 14:39 ` Joel Brobecker
2006-10-12 14:46 ` Andreas Schwab
2006-10-13 15:10 ` Eli Zaretskii
2006-10-13 15:18 ` Daniel Jacobowitz
2006-10-17 20:53 ` 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=20061012055231.GG1059@adacore.com \
--to=brobecker@adacore.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.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