public inbox for
 help / color / mirror / Atom feed
From: Chad Walstrom <>
Subject: Re: gnatsd problems with 4.0.1
Date: Wed, 05 Jan 2005 22:24:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

Tim Buck wrote:
> I'm trying to build gnats 4.0.1 on a FreeBSD 5.3/amd64 platform.  It
> compiles OK, but segfaults when invoked. So I built it with CFLAGS="-g
> -Wall" to get debugging symbols in the binary, but this binary doesn't
> segfault!

Hmm... I know there have been some problems recently with the gcc
compilers, libc, and 4.0.x.  I believe it has something to do with the
memcpy() handling in ./libiberty, especially when compiled with
optimizations turned on.  The suggestion has been to turn off
optimizations when you compile.

This was the reason why I tried to update the ./libiberty and ./include
directories in the CVS version of GNATS.  As you experienced, there are
build problems on the FreeBSD platform involving this upgrade.

> However, the debugging binary doesn't work correctly. Some commands
> (such as DBLS) work, but most EXPR commands return "415 invalid
> expression" (the same expressions work in gnats 4.0).

This is strange.  There were no changes to the regex code between 4.0
and 4.0.1.  Have you tested simple expressions as well as more complex
ones?  If you could share what you've tried, perhaps we can test on our
own as well.

> Since 4.0 seems to work correctly, I'm sticking with it for now.  But
> I'd like to stay current, so if you have any ideas about what's going
> on please share them! I'll be happy to provide further info as needed.

The "exploit" possibility in gnats <= 4.0 is fairly remote, if not well
neigh impossible.  Sticking with gnats 4.0 is fine, though I would like
to make things work for you in 4.0.1.

Chad Walstrom <> 
           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

  reply	other threads:[~2005-01-05 22:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 18:23 Tim Buck
2005-01-05 22:24 ` Chad Walstrom [this message]
2005-01-06  9:18   ` Mike M. Volokhov
2005-01-06 17:07     ` Chad Walstrom
2005-02-07 15:47       ` Mike M. Volokhov
2005-02-07 17:15         ` Mark D. Baushke
2005-02-07 19:17           ` Chad Walstrom
2005-02-09 12:50           ` Removing libiberty (was Re: gnatsd problems with 4.0.1) Mike M. Volokhov
2005-02-09 17:15             ` Mark D. Baushke
2005-02-07 17:45         ` Chad Walstrom
2005-02-09 10:56           ` Mike M. Volokhov
     [not found]             ` <>
     [not found]               ` <>
2005-02-24 22:17                 ` Soon to come: RC3 Chad Walstrom
2005-02-24 22:40                   ` RC2 (was Re: Soon to come: RC3) Chad Walstrom
2005-01-06 16:03   ` gnatsd problems with 4.0.1 Tim Buck

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).