From: Yngve Svendsen <yngve.svendsen@sun.com>
To: "Rajesh K Rajaram" <rrajaram@spatialwireless.com>, <help-gnats@gnu.org>
Subject: Re: gnats.lock file is created and core file is generated.
Date: Thu, 23 Jan 2003 08:25:00 -0000 [thread overview]
Message-ID: <5.2.0.9.0.20030123092129.00bed740@ms-etro01-01.norway.sun.com> (raw)
In-Reply-To: <BLEMIOEJEBNNHJLJJPOGCEHLCFAA.rrajaram@spatialwireless.com>
At 21:00 22.01.2003 -0600, Rajesh K Rajaram wrote:
>Hello All,
>
>We recently added another database ( fourth one) in GNATS for our company.
>The problem is everytime a PR is submitted there is "core file" created on
>/gnats-queue and "gnats.lock file" on /gnats-adm directory. I belive
>submitter file is mismatching and it generates the core file. I'm not
>positive about that!!!
>
>Anyways my questions are
>1) Is there a way I can debug "core" file or "lock" file to find exactly
>what is the problem.
Yes, the core file can be used for debugging. I would much rather recommend
that you look in some of the obvious places first, though. You should
especially look carefully through your categories file and see if any of
the entries have a missing field. Simply counting the number of colons (:)
in each line should be enough. Missing fields in that file is the most
common reason for a coredumping queue-pr/file-pr.
Yngve Svendsen
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
prev parent reply other threads:[~2003-01-23 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 3:04 Rajesh K Rajaram
2003-01-23 8:25 ` Yngve Svendsen [this message]
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=5.2.0.9.0.20030123092129.00bed740@ms-etro01-01.norway.sun.com \
--to=yngve.svendsen@sun.com \
--cc=help-gnats@gnu.org \
--cc=rrajaram@spatialwireless.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).