<br>hi,<br>ok, so i used the where command and also the backtrace full command. I've attached 2 files , one for each command.<br><br>Sisil.<br><div class="gmail_quote">On Sun, Aug 16, 2009 at 12:30 AM, Mathieu Bouchard <span dir="ltr"><<a href="mailto:matju@artengine.ca">matju@artengine.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Sun, 16 Aug 2009, sisil mehta wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Program received signal SIGSEGV, Segmentation fault.<br>
[Switching to Thread 0xb7e5c8d0 (LWP 9989)]<br>
0xb7bbd2eb in handle_braces (ac=1, av=0xbfea9b98) at gridflow.c.fcs:766<br>
766 const char *s = av[i].a_symbol->s_name;<br>
Current language: auto; currently c++<br>
(gdb) Quit<br>
</blockquote>
<br></div>
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.<div>
<div></div><div class="h5"><br>
<br>
_ _ __ ___ _____ ________ _____________ _____________________ ...<br>
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec</div></div></blockquote></div><br>