Uploaded image for project: 'PHP Legacy Driver'
  1. PHP Legacy Driver
  2. PHP-1418

php5-mongo segfault php_mongo_stream_notify_io - Bad permissions for mapped region at address 0x29

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 1.6.5
    • Fix Version/s: None
    • Component/s: pecl-mongo
    • Labels:
      None
    • Environment:
      Debian 7, php-5.5.23-1~dotdeb.1
    • # Replies:
      2
    • Last comment by Customer:
      false

      Description

      Now it crashs on my productive Applikation after Upgrade the php5-* packes yesterday from dotdeb:

      valgrind php dyndns.php                                                                                                                                    [2/9287]
      ==17510== Memcheck, a memory error detector
      ==17510== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
      ==17510== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
      ==17510== Command: php dyndns.php
      ==17510== 
      ==17510== Jump to the invalid address stated on the next line
      ==17510==    at 0x29: ???
      ==17510==    by 0xEFED848: php_mongo_stream_notify_io (in /usr/lib/php5/20121212/mongo.so)
      ==17510==    by 0xEFEBBE1: php_mongo_io_stream_send (in /usr/lib/php5/20121212/mongo.so)
      ==17510==    by 0xEFDB435: php_mongo_runquery (in /usr/lib/php5/20121212/mongo.so)
      ==17510==    by 0xEFE88CB: php_mongo_runcommand (in /usr/lib/php5/20121212/mongo.so)
      ==17510==    by 0xEFE8D4B: ??? (in /usr/lib/php5/20121212/mongo.so)
      ==17510==    by 0x6C1448: dtrace_execute_internal (in /usr/bin/php5)
      ==17510==    by 0x780A3A: ??? (in /usr/bin/php5)
      ==17510==    by 0x740B47: execute_ex (in /usr/bin/php5)
      ==17510==    by 0x6C131C: dtrace_execute_ex (in /usr/bin/php5)
      ==17510==    by 0x7810A5: ??? (in /usr/bin/php5)
      ==17510==    by 0x740B47: execute_ex (in /usr/bin/php5)
      ==17510==  Address 0x29 is not stack'd, malloc'd or (recently) free'd
      ==17510== 
      ==17510== 
      ==17510== Process terminating with default action of signal 11 (SIGSEGV)
      ==17510==  Bad permissions for mapped region at address 0x29
      ==17510==    at 0x29: ???
      ==17510==    by 0xEFED848: php_mongo_stream_notify_io (in /usr/lib/php5/20121212/mongo.so)
      ==17510==    by 0xEFEBBE1: php_mongo_io_stream_send (in /usr/lib/php5/20121212/mongo.so)
      ==17510==    by 0xEFDB435: php_mongo_runquery (in /usr/lib/php5/20121212/mongo.so)
      ==17510==    by 0xEFE88CB: php_mongo_runcommand (in /usr/lib/php5/20121212/mongo.so)
      ==17510==    by 0xEFE8D4B: ??? (in /usr/lib/php5/20121212/mongo.so)
      ==17510==    by 0x6C1448: dtrace_execute_internal (in /usr/bin/php5)
      ==17510==    by 0x780A3A: ??? (in /usr/bin/php5)
      ==17510==    by 0x740B47: execute_ex (in /usr/bin/php5)
      ==17510==    by 0x6C131C: dtrace_execute_ex (in /usr/bin/php5)
      ==17510==    by 0x7810A5: ??? (in /usr/bin/php5)
      ==17510==    by 0x740B47: execute_ex (in /usr/bin/php5)
      ==17510== 
      ==17510== HEAP SUMMARY:
      ==17510==     in use at exit: 7,032,373 bytes in 27,940 blocks
      ==17510==   total heap usage: 32,305 allocs, 4,365 frees, 8,333,078 bytes allocated
      ==17510== 
      ==17510== LEAK SUMMARY:
      ==17510==    definitely lost: 0 bytes in 0 blocks
      ==17510==    indirectly lost: 0 bytes in 0 blocks
      ==17510==      possibly lost: 0 bytes in 0 blocks
      ==17510==    still reachable: 7,032,373 bytes in 27,940 blocks
      ==17510==         suppressed: 0 bytes in 0 blocks
      ==17510== Rerun with --leak-check=full to see details of leaked memory
      ==17510== 
      ==17510== For counts of detected and suppressed errors, rerun with: -v
      ==17510== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 31 from 10)
      Speicherzugriffsfehler
      

      The script proceeded with 90%, it crash with a mongo insert, but if i delete the insert, it crashes.

      At the moment a gdb stack trace is not available.

      Is there a Workaround?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              Bodenhaltung Bodenhaltung [X]
              Participants:
              Last commenter:
              Alexander Golin Alexander Golin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                6 years, 3 weeks, 6 days ago
                Date of 1st Reply: