How to debug a kernel dump that breaks in the dlopen () plugin? Ed?

Question

I have a kernel dump from the user. The main program loads the selected plugins through dlopen. The process is interrupted in the plugin module. The user provided a backtrace that includes the plugin file name and the function in which it was interrupted.

I need to look at data such as arguments passed to a function. How to tell gdb where the plugin was downloaded, so it can figure out how to show the source and data?

Answer 1

How to tell gdb where the plugin was downloaded so that it can figure out how to show the source and data?

GDB ( core).

, , , . . .

Answer 2

, . , . "" , . , , /method.

, , . dlopen , () , , .

bt, .

" ", , . , , gdb . , , . , . !