Bug #83029 MEB prints scary stack trace if it cannot make the initial connection
Submitted: 17 Sep 2016 7:32
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Enterprise Backup Severity:S4 (Feature request)
Version:3.12.3 OS:Linux
Assigned to: CPU Architecture:Any

[17 Sep 2016 7:32] Shane Bester
Description:
provide incorrect user/password when running mysqlbackup, it crashes.

160916 23:40:18 mysqlbackup: WARNING: Can not establish connection to mysql server.
      Connection open fails with error "Access denied for user 'sbester'@'127.0.0.1' (using password: NO)"
 mysqlbackup: INFO: An exceptional situation is detected therefore printing
 stacktrace. mysqlbackup might able to recover from this situation.

stack_bottom = 0 thread_stack 0x10000
./bin/mysqlbackup(my_print_stacktrace+0x2e)[0x5d3aae]
./bin/mysqlbackup(meb::Exception::Exception(meb::enum_error_numbers, char const*, char const*, int)+0x99)[0x4986f9]
./bin/mysqlbackup(meb::Mysql_connection::open()+0x1fe)[0x4c35be]
./bin/mysqlbackup(meb::Mysql_connection::Mysql_connection()+0x8e)[0x4c381e]
./bin/mysqlbackup(meb::Server_util::initialize_server_connection()+0x37)[0x59b2b7]
./bin/mysqlbackup(meb::Server_util::Server_util()+0x81)[0x59b491]
./bin/mysqlbackup(meb::Config_util::init()+0x23)[0x4905e3]
./bin/mysqlbackup(meb::Config_util::init_config()+0xb9)[0x4913d9]
./bin/mysqlbackup(meb::Meb_session::init_session(int, char**)+0xce)[0x4adcae]
./bin/mysqlbackup(meb::mysqlbackup_parallel(int, char**)+0x1a)[0x57b1ea]
./bin/mysqlbackup(main+0xa6)[0x57b3d6]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fdbae5bcaf5]
./bin/mysqlbackup(__gxx_personality_v0+0x311)[0x476779]
 mysqlbackup: ERROR: Connection initialization error.
 mysqlbackup: INFO: An exceptional situation is detected therefore printing
 stacktrace. mysqlbackup might able to recover from this situation.

How to repeat:
provide incorrect user/password when running mysqlbackup, it crashes.
[17 Sep 2016 7:49] MySQL Verification Team
btw,  you need --trace=1  or --trace=2 to see a crash.