Mirrors
/
mariadb
mirror of https://github.com/MariaDB/server
3
0
Fork 0
Code Releases Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
64007 Commits
3333 Branches
1099 Tags
1.3 GiB
Tree: 9827d4aa63
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9827d4aa63'
${ noResults }
mariadb/sql/debug_sync.h

61 lines
2.1 KiB
Raw Normal View History

WL#4259 - Debug Sync Facility Backport from 6.0 to 5.1. Only those sync points are included, which are used in debug_sync.test. The Debug Sync Facility allows to place synchronization points in the code: open_tables(...) DEBUG_SYNC(thd, "after_open_tables"); lock_tables(...) When activated, a sync point can - Send a signal and/or - Wait for a signal Nomenclature: - signal: A value of a global variable that persists until overwritten by a new signal. The global variable can also be seen as a "signal post" or "flag mast". Then the signal is what is attached to the "signal post" or "flag mast". - send a signal: Assign the value (the signal) to the global variable ("set a flag") and broadcast a global condition to wake those waiting for a signal. - wait for a signal: Loop over waiting for the global condition until the global value matches the wait-for signal. Please find more information in the top comment in debug_sync.cc or in the worklog entry.
16 years ago
​
​
Updated/added copyright headers
15 years ago
WL#4259 - Debug Sync Facility Backport from 6.0 to 5.1. Only those sync points are included, which are used in debug_sync.test. The Debug Sync Facility allows to place synchronization points in the code: open_tables(...) DEBUG_SYNC(thd, "after_open_tables"); lock_tables(...) When activated, a sync point can - Send a signal and/or - Wait for a signal Nomenclature: - signal: A value of a global variable that persists until overwritten by a new signal. The global variable can also be seen as a "signal post" or "flag mast". Then the signal is what is attached to the "signal post" or "flag mast". - send a signal: Assign the value (the signal) to the global variable ("set a flag") and broadcast a global condition to wake those waiting for a signal. - wait for a signal: Loop over waiting for the global condition until the global value matches the wait-for signal. Please find more information in the top comment in debug_sync.cc or in the worklog entry.
16 years ago
​
​
​
​
​
​
​
​
​
​
​
Updated/added copyright headers
15 years ago
WL#4259 - Debug Sync Facility Backport from 6.0 to 5.1. Only those sync points are included, which are used in debug_sync.test. The Debug Sync Facility allows to place synchronization points in the code: open_tables(...) DEBUG_SYNC(thd, "after_open_tables"); lock_tables(...) When activated, a sync point can - Send a signal and/or - Wait for a signal Nomenclature: - signal: A value of a global variable that persists until overwritten by a new signal. The global variable can also be seen as a "signal post" or "flag mast". Then the signal is what is attached to the "signal post" or "flag mast". - send a signal: Assign the value (the signal) to the global variable ("set a flag") and broadcast a global condition to wake those waiting for a signal. - wait for a signal: Loop over waiting for the global condition until the global value matches the wait-for signal. Please find more information in the top comment in debug_sync.cc or in the worklog entry.
16 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Bug #51648 DBUG_SYNC_POINT is not defined on all platforms and mtr cant pre-check that DBUG_SYNC_POINT has at least one strong limitation that it's not defined on all platforms. It has issues cooperating with @@debug. All in all its functionality is superseded by DEBUG_SYNC facility and there is no reason to maintain the old less flexible one. Fixed with adding debug_sync_set_action() function as a facility to set up a sync-action in the server sources code and re-writing existing simulations (found 3) to use it. Couple of tests have been reworked as well. The patch offers a pattern for setting sync-points in replication threads where the standard DEBUG_SYNC does not suffice to reach goals.
16 years ago
WL#4259 - Debug Sync Facility Backport from 6.0 to 5.1. Only those sync points are included, which are used in debug_sync.test. The Debug Sync Facility allows to place synchronization points in the code: open_tables(...) DEBUG_SYNC(thd, "after_open_tables"); lock_tables(...) When activated, a sync point can - Send a signal and/or - Wait for a signal Nomenclature: - signal: A value of a global variable that persists until overwritten by a new signal. The global variable can also be seen as a "signal post" or "flag mast". Then the signal is what is attached to the "signal post" or "flag mast". - send a signal: Assign the value (the signal) to the global variable ("set a flag") and broadcast a global condition to wake those waiting for a signal. - wait for a signal: Loop over waiting for the global condition until the global value matches the wait-for signal. Please find more information in the top comment in debug_sync.cc or in the worklog entry.
16 years ago
​
​
​
​
​
​
​
  1. #ifndef DEBUG_SYNC_INCLUDED
  2. #define DEBUG_SYNC_INCLUDED
  4. /* Copyright (c) 2009, 2010, Oracle and/or its affiliates. All rights reserved.
  6. This program is free software; you can redistribute it and/or modify
  7. it under the terms of the GNU General Public License as published by
  8. the Free Software Foundation; version 2 of the License.
  10. This program is distributed in the hope that it will be useful,
  11. but WITHOUT ANY WARRANTY; without even the implied warranty of
  12. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  13. GNU General Public License for more details.
  15. You should have received a copy of the GNU General Public License
  16. along with this program; if not, write to the Free Software
  17. Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA */
  19. /**
  20. @file
  22. Declarations for the Debug Sync Facility. See debug_sync.cc for details.
  23. */
  25. #ifdef USE_PRAGMA_INTERFACE
  26. #pragma interface /* gcc class implementation */
  27. #endif
  29. #include <my_global.h>
  31. class THD;
  33. #if defined(ENABLED_DEBUG_SYNC)
  35. /* Macro to be put in the code at synchronization points. */
  36. #define DEBUG_SYNC(_thd_, _sync_point_name_) \
  37. do { if (unlikely(opt_debug_sync_timeout)) \
  38. debug_sync(_thd_, STRING_WITH_LEN(_sync_point_name_)); \
  39. } while (0)
  41. /* Command line option --debug-sync-timeout. See mysqld.cc. */
  42. extern uint opt_debug_sync_timeout;
  44. /* Default WAIT_FOR timeout if command line option is given without argument. */
  45. #define DEBUG_SYNC_DEFAULT_WAIT_TIMEOUT 300
  47. /* Debug Sync prototypes. See debug_sync.cc. */
  48. extern int debug_sync_init(void);
  49. extern void debug_sync_end(void);
  50. extern void debug_sync_init_thread(THD *thd);
  51. extern void debug_sync_end_thread(THD *thd);
  52. extern void debug_sync(THD *thd, const char *sync_point_name, size_t name_len);
  53. extern bool debug_sync_set_action(THD *thd, const char *action_str, size_t len);
  55. #else /* defined(ENABLED_DEBUG_SYNC) */
  57. #define DEBUG_SYNC(_thd_, _sync_point_name_) /* disabled DEBUG_SYNC */
  59. #endif /* defined(ENABLED_DEBUG_SYNC) */
  61. #endif /* DEBUG_SYNC_INCLUDED */