From: Chad Walstrom <chewie@wookimus.net>
To: bug-gnats@gnu.org
Subject: Re: Preparing 4.1...
Date: Wed, 17 Nov 2004 23:26:00 -0000 [thread overview]
Message-ID: <20041117193346.GF24298@wookimus.net> (raw)
In-Reply-To: <20041104191247.GG30264@wookimus.net>
[-- Attachment #1.1: Type: text/plain, Size: 1068 bytes --]
Chad Walstrom wrote:
> This is a larger change than I had hoped for, but probably one that
> needs to be done.
Update number two. I've tagged the HEAD branch of CVS before adding the
libiberty updates. I intended on branching off HEAD to test this
addition, but messed up my commits, so the libiberty updates are on HEAD
instead of of the libiberty update branch. In any case, I have a few
more cleanup changes to commit tonight.
Note, I'm not getting the coredump issues with the update libiberty
files. When I ran a backtrace on the offending gnatsd executable, it
traced back to the memcpy function in the /lib/tls/libc-2.3.2.so
library. I haven't tracked down the exact updates in libiberty yet to
pinpoint the problem, but because I'm not getting these coredumps, I
think might be able to assume they were fixed.
So, wait for my commits later today, and then please test on your
respective platforms.
--
Chad Walstrom <chewie@wookimus.net> http://www.wookimus.net/
assert(expired(knowledge)); /* core dump */
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 137 bytes --]
_______________________________________________
Bug-gnats mailing list
Bug-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnats
[-- Attachment #3: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2004-11-17 23:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 21:20 CVS, Documentation, TODO Lists, New Maintainer, and Stuff Chad C. Walstrom
2004-06-10 21:44 ` Chad C. Walstrom
2004-06-13 8:51 ` Mel Hatzis
2004-06-13 23:01 ` Andrew Gray
2004-06-11 22:28 ` Yngve Svendsen
2004-06-14 17:07 ` Pankaj K Garg
2004-06-14 17:16 ` Chad C. Walstrom
2004-06-20 17:39 ` PAM Authentication Patch Pankaj K Garg
[not found] ` <gargp@earthlink.net>
2004-06-20 17:59 ` Mark D. Baushke
2004-06-21 7:25 ` Chad Walstrom
2004-06-21 15:26 ` Chad Walstrom
[not found] ` <chewie@wookimus.net>
2004-06-21 15:34 ` Mark D. Baushke
2004-11-04 1:27 ` Preparing 4.1 Mark D. Baushke
2004-11-04 3:15 ` Chad Walstrom
2004-11-04 19:15 ` Chad Walstrom
2004-11-17 23:26 ` Chad Walstrom [this message]
2004-06-21 16:13 ` PAM Authentication Patch Chad Walstrom
2004-10-29 21:33 Preparing 4.1 Chad C. Walstrom
2004-10-31 14:03 ` Pankaj Garg
2004-11-01 19:09 ` Pankaj Garg
2004-11-03 22:39 ` Chad C. Walstrom
2004-11-03 22:46 ` Chad C. Walstrom
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=20041117193346.GF24298@wookimus.net \
--to=chewie@wookimus.net \
--cc=bug-gnats@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).