public inbox for gnats-prs@sourceware.org
help / color / mirror / Atom feed
From: mh@hagos.de
To: gnats-gnats@sourceware.cygnus.com
Subject: gnats/23: gnatsd core
Date: Fri, 05 Nov 1999 01:24:00 -0000	[thread overview]
Message-ID: <19991105091509.10768.qmail@sourceware.cygnus.com> (raw)

>Number:         23
>Category:       gnats
>Synopsis:       gnatsd core
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Nov 05 01:24:01 PST 1999
>Closed-Date:
>Last-Modified:
>Originator:     Klaus Muth
>Release:        3.110
>Organization:
>Environment:
Redhat 6.0 on Intel, uname -a:
Linux falcon.hagos.de 2.2.5-15de #1 Tue May 25 01:00:43 EDT 1999 i586 unknown
>Description:
gnatsd won't talk via inetd.
gnatsd throws core on direct start: gdb:
This GDB was configured as "i386-redhat-linux"...
(no debugging symbols found)...
Core was generated by `/usr/libexec/gnats/gnatsd'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
#0  0x40076e1d in __strdup (s=0x0) at strdup.c:42
strdup.c:42: No such file or directory.

This is the end of my humble debugging knowledge...
>How-To-Repeat:
get the gnats-3.110-4.src.rpm from ftp.redhat.com
/rawhide/powertools/SRPMS and build with rpm -ba gnats.spec

There is a patch, which added .h files in 3 places...
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~1999-11-05  1:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-05  1:24 mh [this message]
1999-11-05  1:34 Jason Molenda

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=19991105091509.10768.qmail@sourceware.cygnus.com \
    --to=mh@hagos.de \
    --cc=gnats-gnats@sourceware.cygnus.com \
    /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).