public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Chad Walstrom <chewie@wookimus.net>
To: help-gnats@gnu.org
Subject: Re: Gnatsweb: Unparseable reply from gnatsd
Date: Wed, 16 Mar 2005 06:43:00 -0000	[thread overview]
Message-ID: <20050315175716.GE31706@wookimus.net> (raw)
In-Reply-To: <20050315173452.GD31706@wookimus.net>


[-- Attachment #1.1: Type: text/plain, Size: 643 bytes --]

On Tue, Mar 15, 2005 at 11:34:52AM -0600, Chad Walstrom wrote:
> Compile with debugging symbols and save the coredump?

Some of the recent compiles of 4.0 had been problematic when compiled
with optimizations.  I believe it had something to do with the libiberty
handling of memcpy and other wrapper functions.  Libiberty has been
removed in 4.1.0, which consequently is considered the new "stable"
platform.  Rather than spending a lot of time debugging 4.0, I would
suggest upgrading if possible.

-- 
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: 140 bytes --]

_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

  reply	other threads:[~2005-03-15 18:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050315170600.3290EE90F1@mail.advancedpricing.com>
2005-03-15 17:54 ` Jeremy Cowgar
2005-03-15 18:11   ` Chad Walstrom
2005-03-16  6:43     ` Chad Walstrom [this message]
2005-03-14 19:41 Jeremy Cowgar
2005-03-14 20:57 ` Chad Walstrom
2005-03-15  3:38   ` Jeremy Cowgar
2005-03-15 17:36     ` Stuart Stevens

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=20050315175716.GE31706@wookimus.net \
    --to=chewie@wookimus.net \
    --cc=help-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).