I expect if you take that route, you would have to compile the Python interpreter with debugging enabled, and then run that with gdb. A better idea might be to recompile your library to produce debugging output at strategic locations, and then output it to the console or a socket to some logging program. Note that the C stdout/stderr usually doesn't correspond to the ones in Python's sys module.
Cheers On Monday 28 April 2008 02:03, tuyun wrote: > Hi > May be this is a basic question, but I havent find answer through google :( > I'm not familiar with python. I wrote a C library, and some body used the > library in his python program, and found a bug of my library, I want to > figure out what's wrong in my library. So how can I make a breakpoint for a > suspect function in my C library when he is "running in " a python program. > Is there a debugger or what, which like gdb, I just need to issue:b > xxxxxxxx? Thanks in advance for my "amateurish question" :( > > Thanks > Twomol > _________________________________________________________________ > 用手机MSN聊天写邮件看空间，无限沟通，分享精彩！ > http://mobile.msn.com.cn/ _______________________________________________ Tutor maillist - Tutor@python.org http://mail.python.org/mailman/listinfo/tutor
