Debugging

[vital valley]

Anybody know how to debug the .so file using valgrind or gdb

[tawny vale]

When your question is answered use !solved to mark the question as resolved.

Remember to ask specific questions, provide necessary details, and reduce your question to its simplest form. For tips on how to ask a good question use !howto ask.

[quick tiger]

You can't debug a .so file, but you can debug a program using a .so file

It's no different than debugging anything else, you can set breakpoints and step around same as you normally would

[vital valley]

You said that the .so file can be read within another source code file or import using python as ctype to debug the .so file

Is this right?

[quick tiger]

No

Not at all

You can simply debug a program utilizing a shared library

[vital valley]

Are you pls explain me clearly?

In our project doesnot have the main() the working mechanism of my project is that the collection of object file can be converted into .so file and use package module to import the python program. So in the scenerio how can I debug it?

[quick tiger]

Thanks for providing additional context on what you're doing

I would say either 1) make a simple test program using your library or 2) you can run gdb on the python interpreter and set breakpoints in your .so

[vital valley]

Is gdb works?

Can we use valgrind or will you know any other best tool to debug the memory leakage?

[quick tiger]

for valgrind I would recommend putting together a simple program with a main() function utilizing your .so

you could try running valgrind on cpython but it'd probably be slow had have a lot of false positives

[vital valley]

Then you recommend gdb is the best option for our scenerio?
Am I right?

After a time it automatically exits due to segmentation fault when I using valgrind

[quick tiger]

I would recommend gdb yes

[vital valley]

Thank you buddy

[tawny vale]

@vital valley Has your question been resolved? If so, type !solved :)

[vital valley]

I don't execute the idea . I can use this and afterwards surely I update my results..
And my question has solved ...

[keen cliff]

It's just a bot that's triggered on itself.
When it reads a message like "Thank you buddy" and then there's a moment of silence (5 minutes in this case) where no other messages arrive, then the bot thinks that the Thank you buddy was meant for another person who helped you solve the question and that you simply forgot to close the question, which is why it reminded you that you could close it.

If it doesn't apply to you, just ignore whatever @tawny vale wrote