On Feb 13, 2013, at 05:18 AM, Prashanth Srinivasan <prashanth93@...> wrote:
Firstly, thanks for the reply.
I ran mged and archer from the command line.
On running mged from the command line, the output is a segmentation fault error message, along with the process id. Running archer gives the same output.
Hm, that's obviously a problem but not enough information to do anything about it. If you know how to get a stack trace, please do submit a bug report: http://sourceforge.net/tracker/?func=add&group_id=105292&atid=640802
You may be able to obtain a stack trace easily if you have gdb installed with these steps:
$ gdb --args /path/to/bin/mged
...
gdb> run
... segfaults
gdb> backtrace
Capture the entire output into a file, include that with your bug report, and we should be able to see what's going wrong.
Cheers!
Sean
|