Menu

#8 Crash/Segfault on mcal_store_event

General_Issues
open
libmcal (9)
5
1999-12-22
1999-12-21
Anonymous
No

Executing the following script causes a crash and segfault, returning a 'document contained no data' or 'unrecognized response' type error...

//start of script

if ($stream = mcal_open( "{/mstore}", "mrobinso", "yada")) {
echo "<br><br>Opened the mstore calendar";
}
else {
echo "Failed opening the mstore calendar";
}
$eventcat = mcal_event_set_category($stream, "Tests");
$eventtitle = mcal_event_set_title($stream, "Test One");
$eventdesc = mcal_event_set_description ($stream, "This is the first test of the mstore drivers for libmcal.");
$eventstart = mcal_event_set_start($stream, 1999, 12, 1 );
mcal_store_event($stream);
echo "<br><br>" . $currentevents->category . "<br><br>";
echo $currentevents->title . "<br><br>";
echo $currentevents->description . "<br><br>";

//end of script

The following is written to the apache error_log:

[Mon Dec 20 13:39:04 1999] [notice] child pid 809 exit signal Segmentation fault (11)
[Mon Dec 20 13:39:54 1999] [notice] child pid 813 exit signal Segmentation fault (11)
[Mon Dec 20 13:39:56 1999] [notice] child pid 814 exit signal Segmentation fault (11)
[Mon Dec 20 13:39:57 1999] [notice] child pid 811 exit signal Segmentation fault (11)
output.c(214) : Freeing 0x080EE8B8 (4097 bytes), script=/home/httpd/html/mcal.php
======
Nothing is written to disk.
If I remove the store_event call, the script behaves as expected.

Discussion

  • Robert Allen

    Robert Allen - 1999-12-22
    • assigned_to: nobody --> markie
    • milestone: 100201 --> General_Issues
     
  • Robert Allen

    Robert Allen - 1999-12-22

    Assigned to Markie For Analysis. -zircote

     
  • Nobody/Anonymous

    This occurs in php3.0.13 as well.
    Same symptoms exactly.

     
  • Nobody/Anonymous

    What version of php are you using? I\'m willing to bet that this crash has been fixed recently, whether you\'re using php3 or php4.

     
  • Chuck Hagenbuch

    Chuck Hagenbuch - 2000-03-05

    I\'m pretty sure that this is fixed. If we don\'t hear from someone who can reproduce this with current code soon, this should be closed.

    (can I have the power to close/change bugs, btw?) -chuck

     

Log in to post a comment.