hi, ok, so i used the where command and also the backtrace full command. I've attached 2 files , one for each command.
Sisil. On Sun, Aug 16, 2009 at 12:30 AM, Mathieu Bouchard <[email protected]>wrote: > On Sun, 16 Aug 2009, sisil mehta wrote: > > Program received signal SIGSEGV, Segmentation fault. >> [Switching to Thread 0xb7e5c8d0 (LWP 9989)] >> 0xb7bbd2eb in handle_braces (ac=1, av=0xbfea9b98) at gridflow.c.fcs:766 >> 766 const char *s = av[i].a_symbol->s_name; >> Current language: auto; currently c++ >> (gdb) Quit >> > > You have to use the «where» command to actually get the backtrace. for > example, this line's error is probably caused because an invalid message was > being processed, but it doesn't show where the invalid message came from, so > I can't tell why it could be invalid. The «where» command usually is able to > tell the caller of this function, and the caller of the caller, and so on. > > > _ _ __ ___ _____ ________ _____________ _____________________ ... > | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec >
where
Description: Binary data
backtrace
Description: Binary data
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
