Hai MySQLians,

I have listed down the log details which shows the mysql server’s normal shutdown and 
improper
shutdown while it got trouble from C coding. 

Log details from c:\mysql\data\mysql.err
´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´
MySql: ready for connections.
Version: '5.0.0-alpha-max-debug'  socket: ''  port: 3306
Error: Freeing unallocated data at line 181,
'C:\build500\build\mysql-5.0.0-alpha\mysys\my_alloc.c'
040224 20:40:01  MySql: Normal shutdown

MySql: ready for connections.
Version: '5.0.0-alpha-max-debug'  socket: ''  port: 3306
040225 10:35:20  MySql: Normal shutdown
040225 10:35:21  InnoDB: Starting shutdown...
040225 10:35:23  InnoDB: Shutdown completed; log sequence number 0 43634
040225 10:35:24  MySql: Shutdown Complete

MySql: ready for connections.
Version: '5.0.0-alpha-max-debug'  socket: ''  port: 3306
Error: Freeing unallocated data at line 181,
'C:\build500\build\mysql-5.0.0-alpha\mysys\my_alloc.c'

Note that my machine don’t have this directory structure and file as 
'C:\build500\build\mysql-5.0.0-alpha\mysys\my_alloc.c'

I have quote these things into MySQL mailing list and waiting for the reply…

        After that I have created sample COBOL coding to work with MySQL prepared 
statements. Error
obtained from mysql_error() inside COBOL coding as;

    *Can't open shared memory. Request event don't create  (2)*

        This error obtained once the execution crossed the mysql_bind_param() function 
and lead to
mysql_error().

Anyhow after restart the server i can able to see the data i intented to insert.

I want to clarify is this related to memory allocation (or) OS un supporting?

thanks 

Arun.


________________________________________________________________________
Yahoo! India Insurance Special: Be informed on the best policies, services, tools and 
more. 
Go to: http://in.insurance.yahoo.com/licspecial/index.html

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to