[MXS-700] Segfault on startup Created: 2016-04-28  Updated: 2016-04-28  Resolved: 2016-04-28

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 1.4.2
Fix Version/s: 1.4.3

Type: Bug Priority: Major
Reporter: Guillaume Ceccarelli Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

Gentoo, MySQL server versions 5.6.27 (source builds)


 Description   

MaxScale crashes on startup with the following backtrace:

2016-04-28 11:16:58   error  : Commit ID: source-build System name: Linux Release string: NAME=Gentoo Embedded library version: (null)
 
2016-04-28 11:16:58   error  :   maxscale(+0x42d1) [0xef54e4482d1] 
2016-04-28 11:16:58   error  :   /lib64/libpthread.so.0(+0x11630) [0x71b8fdfe0630] 
2016-04-28 11:16:58   error  :   /lib64/libc.so.6(+0x9cead) [0x71b8fd839ead] 
2016-04-28 11:16:58   error  :   //usr/lib64/maxscale/libmaxscale-common.so.1.0.0(check_service_permissions+0x3da) [0x71b8fe49ea3d] 
2016-04-28 11:16:58   error  :   //usr/lib64/maxscale/libmaxscale-common.so.1.0.0(serviceStart+0x3f) [0x71b8fe4c00eb] 
2016-04-28 11:16:58   error  :   //usr/lib64/maxscale/libmaxscale-common.so.1.0.0(serviceStartAll+0x4d) [0x71b8fe4c02c7] 
2016-04-28 11:16:58   error  :   maxscale(main+0x1641) [0xef54e44b393] 
2016-04-28 11:16:58   error  :   /lib64/libc.so.6(__libc_start_main+0xfc) [0x71b8fd7bd7cc] 
2016-04-28 11:16:58   error  :   maxscale(_start+0x29) [0xef54e447a19]

I've tracked the problem down to the following commit: https://github.com/mariadb-corporation/MaxScale/commit/7f18c579a4615eb505e8fee89aacd213f704223d

It looks like in my setup, server->server->server_string is NULL at that point, causing the crash in the strstr call.

Please let me know if I can do anything further with regards to testing or providing you with more information.

 Comments   
Comment by Johan Wikman [ 2016-04-28 ]

Thank's for reporting this. We've been able to reproduce this and will make a 1.4.3 as soon as possible.

Comment by markus makela [ 2016-04-28 ]

The server_string is now properly initialized if it isn't yet.

Generated at Thu Feb 08 04:01:17 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.