[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Unparseable replies from GNATS server
From: |
Stuart Stevens |
Subject: |
RE: Unparseable replies from GNATS server |
Date: |
Wed, 4 Aug 2004 19:49:21 -0700 |
In edit.c, set_field is being called with old_value set to 0x00.
if ((old_value == NULL && new_value != NULL)
|| (new_value == NULL && old_value != NULL)
|| (new_value != old_value && strcmp (old_value, new_value) != 0))
{
/* Ignore changes to readonly fields. */
if (fieldDefForIndex (field)->readonly)
{
fieldsChanged[x] = 0;
set_field (new_pr, field, old_value, err);
}
else
{
fieldsChanged[x] = 1;
}
}
-----Original Message-----
From: Stuart Stevens [mailto:address@hidden
Sent: Wednesday, August 04, 2004 5:08 AM
To: 'Stuart Stevens'; address@hidden
Subject: RE: Unparseable replies from GNATS server
I am running GNATS 4.0 on Linux - Red Hat 9. I pulled the TOT and rebuilt
this morning. I then run the daemon directly and I got a memory fault. The
daemon fails with the following field "Comment-new" added to dbconfig:
field "Comments" {
multitext
read-only
}
field "Comment-new" {
multitext
on-change {
append-to-field "Comments" {
"Comment added by %s on %D\n\n%s"
"$EditUserEmailAddress" "$CurrentDate" "$NewValue"
}
}
on-change {
set-field "Comment-new" {
""
}
}
}
I issued the following commands:
lock 2511 stuart
editaddr stuart
edit 2511
<email with changes>
Next step is to get into the debugger.
Any ideas?
Thanks
Stuart