From: Tim Buck <tbuck@rrinc.com>
To: help-gnats@gnu.org
Subject: gnatsd problems with 4.0.1
Date: Wed, 05 Jan 2005 18:23:00 -0000 [thread overview]
Message-ID: <D3F91AEA-5F46-11D9-95F4-000393C83AC4@rrinc.com> (raw)
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!
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).
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.
Tim Buck * Information Technology Manager * Recognition Research, Inc.
PHONE +1 540 961-6500 * FAX +1 540 961-3568 * EMAIL tbuck@rrinc.com
No one ever went broke underestimating the intelligence of the
American People -- P. T. Barnum
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
next reply other threads:[~2005-01-05 18:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 18:23 Tim Buck [this message]
2005-01-05 22:24 ` Chad Walstrom
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] ` <20050221235730.GC31157@wookimus.net>
[not found] ` <20050222175714.30bc1593.mishka@apk.od.ua>
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:
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=D3F91AEA-5F46-11D9-95F4-000393C83AC4@rrinc.com \
--to=tbuck@rrinc.com \
--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).