There's a bit of confusion here. The builds at mariadb.com should not contain debug symbols, but symbol information.

But the packages at mariadb.com already do that (at least CentOS 6 and CentOS 7). That is, given a stacktrace containing only module + address information, the source file + line can be digged out using the current packages. Instructions for doing this is found here https://github.com/mariadb-corporation/MaxScale/wiki/Debugging and the program script/stacktrace in the MaxScale distribution can do that automatically.

However, it is confusing that the stacktraces pasted to Jira typically (it seems) do not contain sourcecode + line information, but only module + address. Namely, that information is logged explicitly by MaxScale itself, using system functions that should provide the symbolic information.

But there should be packages that have extra checking turned on. That way, if someone is experiencing problems we could instruct them to use such a package instead, in which case problems will hopefully be detected before they manifest themselves as a crash. Timofey is working on that now.

johan.wikman So there are two requests
(1) Include debug symbols in the packages
(2) Provide line number and source code file in the stacktrace -

1. (2) is addressed with the information you provided in the wiki page, in addition to which we still need debug symbols in the packages - so that when we get coredump from field, the coredump can be loaded in debugger with easy to use information.

johan.wikman tturenko Any update on this ?

Thanks,
Dipti

all builds by default contains debug symbols now. closing