MySQL Bugs: #114987: Workbench crashes in SQLServer to MySQL Migration wizard

Bug #114987	Workbench crashes in SQLServer to MySQL Migration wizard
Submitted:	13 May 16:03	Modified:	5 Jul 6:34
Reporter:	Daniël van Eeden (OCA)	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: Migration	Severity:	S1 (Critical)
Version:	8.0.36	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	crash, sigabrt, SQLServer, stack smashing detected

Description:
When trying to migrate a SQL Server database to MySQL with Workbench the application crashes when trying a connection.

The crash report contains: 
*** stack smashing detected ***: terminated

This happens on Ubuntu 22.04 and on Fedora 40 (with fc38 RPM).

How to repeat:
1. Run SQL Server in a container or elsewhere
2. Ensure connectivity with 'tsql'
3. Run Workbench and go to the migration wizard and select SQL Server and enter the connection details where needed. 
4. Click "Test Connection"

dveeden@ununtu2204:~$ WB_DEBUG=gdb mysql-workbench
Found /lib/x86_64-linux-gnu/libproj.so.22
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/mysql-workbench-bin...
Reading symbols from /usr/lib/debug/.build-id/b1/c9150342f1fa575165435b41a12f2f9791c6a1.debug...
(No debugging symbols found in /usr/lib/debug/.build-id/b1/c9150342f1fa575165435b41a12f2f9791c6a1.debug)
(gdb) r
Starting program: /usr/bin/mysql-workbench-bin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffecf07640 (LWP 8037)]
[New Thread 0x7fffe7fff640 (LWP 8038)]
[New Thread 0x7fffe77fe640 (LWP 8039)]
[New Thread 0x7fffe6ffd640 (LWP 8040)]
[Thread 0x7fffe77fe640 (LWP 8039) exited]
[Detaching after fork from child process 8042]
[Detaching after fork from child process 8043]
[Detaching after fork from child process 8044]
[Detaching after fork from child process 8046]
[New Thread 0x7fffe4a95640 (LWP 8047)]
[Thread 0x7fffe4a95640 (LWP 8047) exited]
[New Thread 0x7fffe4a95640 (LWP 8048)]
[New Thread 0x7fffd7fff640 (LWP 8049)]
[Thread 0x7fffe4a95640 (LWP 8048) exited]
[Thread 0x7fffd7fff640 (LWP 8049) exited]
[New Thread 0x7fffd7fff640 (LWP 8050)]
[New Thread 0x7fffe4a95640 (LWP 8051)]
[Thread 0x7fffd7fff640 (LWP 8050) exited]
[Thread 0x7fffe4a95640 (LWP 8051) exited]
[New Thread 0x7fffe4a95640 (LWP 8052)]
[Detaching after fork from child process 8053]
[Detaching after fork from child process 8059]
[Detaching after fork from child process 8060]
[New Thread 0x7fffd7fff640 (LWP 8061)]
[New Thread 0x7fffd7432640 (LWP 8065)]
[New Thread 0x7fffd6c31640 (LWP 8066)]
[Thread 0x7fffd7432640 (LWP 8065) exited]
[Thread 0x7fffd6c31640 (LWP 8066) exited]
[New Thread 0x7fffd6c31640 (LWP 8067)]
[New Thread 0x7fffd7432640 (LWP 8068)]
[Thread 0x7fffd6c31640 (LWP 8067) exited]
[Thread 0x7fffd7432640 (LWP 8068) exited]
[New Thread 0x7fffd7432640 (LWP 8069)]
[New Thread 0x7fffd6c31640 (LWP 8070)]
[Thread 0x7fffd7432640 (LWP 8069) exited]
[Thread 0x7fffd6c31640 (LWP 8070) exited]
[New Thread 0x7fffd6c31640 (LWP 8071)]
[New Thread 0x7fffd7432640 (LWP 8072)]
[Thread 0x7fffd6c31640 (LWP 8071) exited]
[Thread 0x7fffd7432640 (LWP 8072) exited]
[New Thread 0x7fffd7432640 (LWP 8073)]
[New Thread 0x7fffd6c31640 (LWP 8074)]
[Thread 0x7fffd7432640 (LWP 8073) exited]
[Thread 0x7fffd6c31640 (LWP 8074) exited]
[New Thread 0x7fffd6c31640 (LWP 8075)]
[New Thread 0x7fffd7432640 (LWP 8076)]
[Thread 0x7fffd6c31640 (LWP 8075) exited]
[Thread 0x7fffd7432640 (LWP 8076) exited]
[New Thread 0x7fffd7432640 (LWP 8078)]
[New Thread 0x7fffd6c31640 (LWP 8079)]
[Thread 0x7fffd7432640 (LWP 8078) exited]
[Thread 0x7fffd6c31640 (LWP 8079) exited]
*** stack smashing detected ***: terminated

Thread 1 "mysql-workbench" received signal SIGABRT, Aborted.
__pthread_kill_implementation (no_tid=0, signo=6, threadid=140737175752384) at ./nptl/pthread_kill.c:44
44	./nptl/pthread_kill.c: No such file or directory.
(gdb)

Hello Daniël van Eeden,

Thank you for the bug report.
I tried to reproduce your issue on Ubuntu 22.04 with workbench 8.0.36 and 8.0.38  but I am not seeing any issues at my end. 

Regards,
Ashwini Patil

I also wasn't able to reproduce this with:
- Fedora 40 x86-64
- MySQL Workbench 8.0.38 build 4270059 CE
- Microsoft SQL Server 2022 (RTM-CU13) (KB5036432) - 16.0.4125.3 (X64)
  - From mcr.microsoft.com/mssql/rhel/server:2022-latest container image