An error occurred fetching the project authors.
  1. 20 May, 2001 1 commit
    • tonu@x3.internalnet's avatar
      .del-vio-global.h~c261412c01b2f4 Delete: vio/vio-global.h · 32477ab4
      tonu@x3.internalnet authored
      .del-viotypes.h~f5a38e7326bd50f3	Delete: vio/viotypes.h
      .del-violite.h~58d2942a52ea7a83	Delete: vio/violite.h
      .del-VioSSLFactoriesFd.h~1d63ae149a63f85	Delete: vio/VioSSLFactoriesFd.h
      .del-VioPipe.cc~12cf83b9a2f48f6c	Delete: vio/VioPipe.cc
      .del-VioSSLAcceptorFd.cc~4c828f3688ed74ec	Delete: vio/VioSSLAcceptorFd.cc
      .del-VioSSL.cc~6e85340b11fa42a8	Delete: vio/VioSSL.cc
      .del-VioSSLFactoriesFd.cc~89f6bf5073937947	Delete: vio/VioSSLFactoriesFd.cc
      .del-vioelitexx.cc~3eaba70da792a7fc	Delete: vio/vioelitexx.cc
      .del-version.cc~7237acf12bed4a97	Delete: vio/version.cc
      .del-VioSocket.cc~71c615783f29b5e1	Delete: vio/VioSocket.cc
      .del-VioSSL.h~70d367b7ec8cac3e	Delete: vio/VioSSL.h
      .del-VioPipe.h~21cebbe61a1da546	Delete: vio/VioPipe.h
      .del-VioFd.h~8294293a88c7b4b8	Delete: vio/VioFd.h
      .del-VioFd.cc~6e444647affef63b	Delete: vio/VioFd.cc
      .del-VioConnectorFd.h~58bc11cdc885b951	Delete: vio/VioConnectorFd.h
      .del-VioAcceptorFd.cc~a5a08947a31f88de	Delete: vio/VioAcceptorFd.cc
      .del-VioConnectorFd.cc~ddbd7821c43c83a2	Delete: vio/VioConnectorFd.cc
      .del-VioAcceptorFd.h~7f9c4358477ba9a3	Delete: vio/VioAcceptorFd.h
      .del-Vio.cc~60737ce02ab2bc25	Delete: vio/Vio.cc
      .del-Vio.h~f4416b2949647602	Delete: vio/Vio.h
      .del-VioSocket.h~a26d535bd5a1a6	Delete: vio/VioSocket.h
      32477ab4
  2. 15 May, 2001 2 commits
  3. 13 May, 2001 2 commits
  4. 12 May, 2001 3 commits
  5. 11 May, 2001 3 commits
  6. 10 May, 2001 5 commits
    • sasha@mysql.sashanet.com's avatar
    • sasha@mysql.sashanet.com's avatar
      7c9b9f47
    • sasha@mysql.sashanet.com's avatar
      sql/mysqld.cc · 4e04aa4a
      sasha@mysql.sashanet.com authored
          put back the things that the merge removed
      4e04aa4a
    • sasha@mysql.sashanet.com's avatar
      merged · c77547ea
      sasha@mysql.sashanet.com authored
      c77547ea
    • sasha@mysql.sashanet.com's avatar
      stack trace updates: · e809e2df
      sasha@mysql.sashanet.com authored
      limited support on Alpha - in general case, even with frame pointer,
      stack trace on alpha is impossible without looking at the symbol table
      frame pointer does get saved on the stack, but you have no idea where
      and where the return address is saved. So the best we can do without
      the symbol table is look for magic opcodes and try to guess how big 
      each frame is and where the return address was hidden from the 
      instruction parameters. In practice, we can usually go up 3-4 frames 
      before we hit some nasty frame that the current code cannot figure
      out. This is actually not too bad, especially when we already have the query
      
      Also cleaned up messages, print more variables, tell the user of
      how much memory mysqld could potentially use, and warn of
      what can happen with default STACK_SIZE and a lot of connections if
      coredump happens when there are more than 200 connections. 
      e809e2df
  7. 09 May, 2001 4 commits
  8. 07 May, 2001 1 commit
  9. 05 May, 2001 2 commits
  10. 04 May, 2001 2 commits
  11. 03 May, 2001 13 commits
  12. 02 May, 2001 2 commits