Bug#36027494 Add mtr test for my_print_stacktrace

Add an mtr test which is only inteded to be run manually:
  ./mtr --no-check-testcases print_stacktrace
Inspect output in var/log/msqld.1.err

Change-Id: Ia308592441df0e4a23a18c590df867a15882cbef

Bug#36027494 Add mtr test for my_print_stacktrace

Add an mtr test which is only inteded to be run manually:
  ./mtr --no-check-testcases print_stacktrace
Inspect output in var/log/msqld.1.err

Change-Id: Ia308592441df0e4a23a18c590df867a15882cbef

Bug#36066725 Regular mgmd hangs when sending it a stop node for ndbmtd

Root cause is that the mutexes 'theMultiTransporterMutex' and
'clusterMgrThreadMutex' are taken in different order in the
two respective call chains:

1) ClusterMgr::threadMain() -> lock() -> NdbMutex_Lock(clusterMgrThreadMutex)
   - ::threadMain(), holding clusterMgrThreadMutex -> TransporterFacade::startConnecting()
     - TF::startConnecting -> lockMultiTransporters()  <<<< HANG while holding clusterMgrThreadMutex

2) TransporterRegistry::report_disconnect() -> lockMultiTransporters()
   - ::report_disconnect(), holding theMultiTransporterMutex, -> TransporterFacade::reportDisconnect()
     - TF::reportDisconnect -> ClusterMgr::reportDisconnected()
       - ClusterMgr::reportDisconnected() -> lock()
         - lock() -> NdbMutex_Lock(clusterMgrThreadMutex) <<<< Held by 1)

Patch change TransporterRegistry::report_disconnect() such that the
theMultiTransporterMutex is released before calling reportDisconnect(NodeId).

It should be sufficient to hold theMultiTransporterMutex while
::report_disconnect check if we are disconnecting a multiTransporter,
and if all its Trps are in DISCONNECTED state. When this
finished we have set up 'ready_to_disconnect' and can release
theMultiTransporterMutex before -> reportDisconnect()

Change-Id: I19be0d9d92184efb8f20a92aa7189b9b85f069bc

Bug#35846221: Assertion Failure in /mysql-8.0.34/sql/field.cc:7119

Problem is due to missing implementation of
Item_func_make_set::fix_after_pullout(), which makes this particular
MAKE_SET function be regarded as const and may thus be evaluated
during resolving.

Fixed by implementing a proper fix_after_pullout() function.

Change-Id: I7094869588ce4133c4a925e1a237a37866a5bb3c
(cherry picked from commit a9f0b388adeef837811fdba2bce2e4ba5b06863b)

Bug#35846221: Assertion Failure in /mysql-8.0.34/sql/field.cc:7119

Problem is due to missing implementation of
Item_func_make_set::fix_after_pullout(), which makes this particular
MAKE_SET function be regarded as const and may thus be evaluated
during resolving.

Fixed by implementing a proper fix_after_pullout() function.

Change-Id: I7094869588ce4133c4a925e1a237a37866a5bb3c
(cherry picked from commit a9f0b388adeef837811fdba2bce2e4ba5b06863b)

Bug#36066725 Regular mgmd hangs when sending it a stop node for ndbmtd

Root cause is that the mutexes 'theMultiTransporterMutex' and
'clusterMgrThreadMutex' are taken in different order in the
two respective call chains:

1) ClusterMgr::threadMain() -> lock() -> NdbMutex_Lock(clusterMgrThreadMutex)
   - ::threadMain(), holding clusterMgrThreadMutex -> TransporterFacade::startConnecting()
     - TF::startConnecting -> lockMultiTransporters()  <<<< HANG while holding clusterMgrThreadMutex

2) TransporterRegistry::report_disconnect() -> lockMultiTransporters()
   - ::report_disconnect(), holding theMultiTransporterMutex, -> TransporterFacade::reportDisconnect()
     - TF::reportDisconnect -> ClusterMgr::reportDisconnected()
       - ClusterMgr::reportDisconnected() -> lock()
         - lock() -> NdbMutex_Lock(clusterMgrThreadMutex) <<<< Held by 1)

Patch change TransporterRegistry::report_disconnect() such that the
theMultiTransporterMutex is released before calling reportDisconnect(NodeId).

It should be sufficient to hold theMultiTransporterMutex while
::report_disconnect check if we are disconnecting a multiTransporter,
and if all its Trps are in DISCONNECTED state. When this
finished we have set up 'ready_to_disconnect' and can release
theMultiTransporterMutex before -> reportDisconnect()

Change-Id: I19be0d9d92184efb8f20a92aa7189b9b85f069bc

Bug#35897778: Upgrade to CURL 8.4.0 [remove old]

Remove all old source files.

Change-Id: Ib46488f2bee755920c21ef2c7768ffa0ab0a9be7

Bug#35897778: Upgrade to CURL 8.4.0 [remove old]

Remove all old source files.

Change-Id: Ifb43e581715178079b5a5a6e0ebcf201d2aae8f2

Bug#35897778: Upgrade to CURL 8.4.0 [remove old]

Remove all old source files.

Change-Id: Ib46488f2bee755920c21ef2c7768ffa0ab0a9be7

Bug#35897778: Upgrade to CURL 8.4.0 [remove old]

Remove all old source files.

Change-Id: Ifb43e581715178079b5a5a6e0ebcf201d2aae8f2