Bug#24924: shared-memory-base-name that is too long causes buffer overflow

show that shm communication still works on windows,
and that we can't overflow the base-name.


mysql-test/t/windows_shm-master.opt:
  Bug#24924: shared-memory-base-name that is too long causes buffer overflow
  
  start a server with shm communication if we're on
  windows.
mysql-test/t/windows_shm.test:
  Bug#24924: shared-memory-base-name that is too long causes buffer overflow
  
  .opt has started a server with shm communication
  if we're on windows. now start a client with shm
  and connect to that server.

mysql-test/r/windows_shm.result

+mysqld is alive
+End of 5.0 tests.

mysql-test/t/windows_shm-master.opt

+--skip-grant-tables --loose-shared-memory-base-name=HeyMrBaseNameXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --loose-shared-memory=1

mysql-test/t/windows_shm.test

+# Windows-specific tests
+--source include/windows.inc
+
+#
+# Bug #24924: shared-memory-base-name that is too long causes buffer overflow
+#
+--exec $MYSQLADMIN --no-defaults --shared-memory-base-name=HeyMrBaseNameXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ping
+
+--echo End of 5.0 tests.