Use the run time option -on_error_abort then it aborts at exactly the line it finds the problem; this is a good option when you run in the debugger. Note that if you use the option -start_in_debugger or -on_error_attach_debugger it automatically does the abort on error detection.
Barry On Aug 2, 2010, at 3:52 PM, John-Michael Fischer wrote: > I was wondering if when PETSC is compiled with-debugging=1 (or any other > configure flag for that matter) I can get it to report the line and filename > that errors occur on in my source. > > It's dutifully reporting the file and line # of the PETSC source, but I know > the error is mine and not a problem with petsc (the error is [0]PETSC ERROR: > Argument out of range! ). > > Since PETSC catches it, even when I run the program in GDB it doesn't > segfault or anything so execution just keeps on going. > > > Thanks > John-Michael Fischer
