Hello. I tried to track the mapD code with GDB, but I failed to step into the function of ‘Executor’. Is there any solution to debug it? Thanks.
The reason for that specific behavior might be related to how you are stepping into gdb. When you try and step in it might step into a c_library function and not into mapd source code.
The call to executor goes through a timer function which we use to measure execution time of the query. The timer function takes the relation algebra executor function as a lambda.
solution: Please try and break specific functions directly if you feel gdb is hopping around. The healthy use of lambdas and functors might throw gdb off some times.
Please let us know if you have any other problems.
Thanks for your reply. It’s very helpful.