GDB would could work. Here's how I use it to track down problems in a C
++ program controlled by python.
$ gdb python
GDB starts up, now at the gdb prompt, set the program args
(gdb) set arg testscript.py
(gdb) run
... program running until crash
(gdb) where
gives you the backtrace if you compile
James Stroud <[EMAIL PROTECTED]> writes:
> Hello All,
>
> The built-in mac osx vecLib is segfaulting in some cases--A very fun
> fact to find out the hard way over two nights of work. I also spent an
> embarrassing amount of time figuring out just where. Although I'm in
> quite a self-congratulat
After a night's rest, I was able to add a function trace to pydb,
command option --fntrace, short option -F, and set/show command
"fntrace".
It's still a little bit funky. (Hey, I didn't get *that* good of a
rest). But it's out there in pydb's CVS in case folks want to try it.
Also, following an
On Apr 6, 8:13 am, James Stroud <[EMAIL PROTECTED]> wrote:
> Hello All,
>
> The built-in mac osx vecLib is segfaulting in some cases--A very fun
> fact to find out the hard way over two nights of work. I also spent an
> embarrassing amount of time figuring out just where. Although I'm in
> quite a
On Apr 6, 7:13 am, James Stroud <[EMAIL PROTECTED]> wrote:
> Hello All,
>
> The built-in mac osx vecLib is segfaulting in some cases--A very fun
> fact to find out the hard way over two nights of work. I also spent an
> embarrassing amount of time figuring out just where. Although I'm in
> quite a
Hello All,
The built-in mac osx vecLib is segfaulting in some cases--A very fun
fact to find out the hard way over two nights of work. I also spent an
embarrassing amount of time figuring out just where. Although I'm in
quite a self-congratulatory mood right now, in the future, I feel like I
c
