#1097 segmentation fault on export

closed
nobody
None
5
2009-03-18
2009-02-24
Marcel Berteler
No

We are experiencing segmentation faults during export of data. This results in either partial data to be displayed on screen or white screens when using the option to save to file.
We where using php 5.1.6 and phpMyAdmin 2.11.9.4 on Linux

After upgrading the php 5.2.6 and phpMyAdmin 3.1.2 the problem still occurred.

I finally tracked this down to a problem with the mysql_unbuffered_query() function. When changing this function to a normal mysql_query() function in mysql.dbi.lib.php the problem disappeared.

I know this is not really a phpMyAdmin problem, is it not possible to add a setting in the config to switch the use of mysql_unbuffered_query() on and off so other people experiencing this problem can at least still make use of phpMyAdmin?

Marcel

Discussion

  • Jürgen Wind
    Jürgen Wind
    2009-02-25

    php 5.1.5/6 had serious bugs (two years ago?)

     
  • Marc Delisle
    Marc Delisle
    2009-02-25

    Also, if your server has a problem with this function, there might be other problems.

    Any hint about having a MySQL client library not matching the MySQL server itself?

    I don't remember having seen such a problem so adding a setting for your particular server problem is overkill.

     
  • Marc Delisle
    Marc Delisle
    2009-02-25

    • status: open --> pending
     
    • status: pending --> open
     
  • lem9: There is on more problem but I have not really done a deeper investigation to what causes that, but all problems just manifest themselves in phpMyAdmin, even after the upgrade. The application that we wrote using Symfony framwork has no issues what so ever.

    windkiel: That is why I updated to 5.2.6 as I though PHP was the problem.

     
  • Marc Delisle
    Marc Delisle
    2009-02-27

    • labels: 546627 -->
    • milestone: 897257 -->
    • status: open --> pending
     
  • Marc Delisle
    Marc Delisle
    2009-02-27

    Any hint about having a MySQL client library not matching the MySQL server
    itself?

     
  • This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
    • status: pending --> closed