1. 21 Jun, 2007 6 commits
    • iggy@amd64.(none)'s avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0-maint · 1378e94a
      iggy@amd64.(none) authored
      into  amd64.(none):/src/bug27029/my50-bug27029
      1378e94a
    • iggy@amd64.(none)'s avatar
      Bug#27029 alter table ... enable keys crashes mysqld on large table · 39416f50
      iggy@amd64.(none) authored
      - When creating an index for the sort, the number of rows plus 1 is used 
      to allocate a buffer.  In this test case, the number of rows 4294967295 
      is the max value of an unsigned integer, so when 1 was added to it, a 
      buffer of size 0 was allocated causing the crash.
      - Create new test suite for this bug's test suite as per QA.
      39416f50
    • msvensson@pilot.(none)'s avatar
    • msvensson@pilot.(none)'s avatar
      Merge pilot.(none):/data/msvensson/mysql/bug28769/my50-bug28769 · c021fc9a
      msvensson@pilot.(none) authored
      into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint
      c021fc9a
    • msvensson@pilot.(none)'s avatar
      Merge pilot.(none):/data/msvensson/mysql/bug28742/my50-bug28742 · f3f1c8c1
      msvensson@pilot.(none) authored
      into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint
      f3f1c8c1
    • tnurnberg@sin.intern.azundris.com's avatar
      Bug#24924: shared-memory-base-name that is too long causes buffer overflow · 3c1be000
      tnurnberg@sin.intern.azundris.com authored
      long shared-memory-base-names could overflow a static internal buffer
      and thus crash mysqld and various clients.  change both to dynamic
      buffers, show everything but overflowing those buffers still works.
      
      The test case for this would pretty much amount to
      mysqld --shared-memory-base-name=HeyMrBaseNameXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --shared-memory=1 &
      mysqladmin --no-defaults --shared-memory-base-name=HeyMrBaseNameXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX shutdown
      
      Unfortunately, we can't just use an .opt file for the
      server. The .opt file is used at start-up, before any
      include in the actual test can tell mysqltest to skip
      this one on non-Windows. As a result, such a test would
      break on unices.
      
      Fixing mysql-test-run.pl to export full path for master
      and slave would enable us to start a server from within
      the test which is ugly and, what's more, doesn't work as
      the server blocks (mysqltest offers no fire-and-forget
      fork-and-exec), and mysqladmin never gets run.
      
      Making the test rpl_windows_shm or some such so we can
      is beyond ugly. As is introducing another file-name based
      special case (run "win*.test" only when on Windows). As is
      (yuck) coding half the test into mtr (as in, having it
      hand out a customized environment conductive to the shm-
      thing on Win only).
      
      Situation is exacerbated by the fact that .sh is not
      necessary run as expected on Win.
      
      In short, it's just not worth it. No test-case until we
      have a new-and-improved test framework.
      3c1be000
  2. 20 Jun, 2007 1 commit
  3. 19 Jun, 2007 5 commits
  4. 18 Jun, 2007 7 commits
  5. 17 Jun, 2007 8 commits
  6. 16 Jun, 2007 3 commits
  7. 15 Jun, 2007 10 commits