http://bugzilla.lysator.liu.se/show_bug.cgi?id=1005
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Keywords|inpro |
Resolution| |FIXED
------- Additional Comments From ceder(a)lysator.liu.se 2003-03-23 23:23 -------
lyskomd.0/36.exp triggered the assertion. copy_membership has now been
fixed, and the test suite now passes again.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1005
------- Additional Comments From ceder(a)lysator.liu.se 2003-03-23 00:21 -------
do_query_read_texts() only sets read_ranges to smalloc(0) when the
want_read_ranges argument is false, and that only happens when called
from query_read_texts() (request 107). That request outputs a new-style
Membership, which never calls prot_a_output_read_texts(). So this call
chain can never trigger the assertion.
This leaves the copy_membership() function. The following possible call
chains exist:
copy_membership
copy_membership_list
copy_person
cached_get_person_stat (when a snapshot exists)
pre_sync (when a dirty locked person exists)
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1005
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Keywords| |inpro
Target Milestone|--- |2.1.0
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1005
Summary: assertion triggered in prot_a_output_read_texts()
Product: lyskomd
Version: 2.0.7
Platform: All
OS/Version: All
Status: NEW
Severity: critical
Priority: P1
Component: server
AssignedTo: ceder(a)lysator.liu.se
ReportedBy: ceder(a)lysator.liu.se
QAContact: lyskomd-qa(a)lists.lysator.liu.se
The following assertion was triggered on RydKOM, which was running a
pre-release of 2.1.0 at the time.
lyskomd: prot-a-output.c:166: prot_a_output_read_texts: Assertion
`mship->no_of_read_ranges > 0' failed.
No core file was created, due to stupid Linux ulimit defaults. The bug
has so far not been possible to recreate.
Preliminary analysis: copy_membership() and do_query_read_texts() can both
set read_reanges to smalloc(0) when no_of_read_ranges is 0. All other
code expects read_ranges to be set to NULL in that case. I'm now attempting
to write test cases that trigger the assertion.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=998
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=997
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P2 |P1
------- Additional Comments From ceder(a)lysator.liu.se 2003-03-10 22:08 -------
If we (the LysKOM collective) want to become immortal through the texts
that we write, it is important that we fix this before we die. Increasing
the priority.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=855
------- Additional Comments From ceder(a)lysator.liu.se 2003-03-08 14:16 -------
A cross-reference aux-item is a more general feature. As such, is does not
convey as much information as the related-conference aux-item would.
On the other hand, cross-reference might be close enough to the wanted
functionality.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=997
------- Additional Comments From 5210(a)lyskom.lysator.liu.se 2003-03-03 22:31 -------
(If should say "conferences" instead of "meetings" for course. I don't know why
I got it wrong in this one when I got it right in bug 998...)
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=855
------- Additional Comments From jhs(a)lysator.liu.se 2003-03-03 21:15 -------
Is this not already implemented via the aux items used for cross references?
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=948
------- Additional Comments From jhs(a)lysator.liu.se 2003-03-03 21:08 -------
Committee supervisorship probably introduces further issues, if something
is to be done about this issue - perhaps joining a supervising conference
would require prompting the joining person for whether she really wants
to accept the shared responsibility she is about to take on?
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.