[petsc-users] Issue about matsetvalues when turn off debugging

[Barry Smith]

On Dec 19, 2013, at 10:47 PM, Gavin Ge <jianchaoge at gmail.com> wrote:

> Thanks Barry. The problem is that the debugging couldn't detect any problem with the debugger. The crash only show up when debugger is turned off.

   I understand. This kind of bug is often (usually?) a result of memory corruption earlier in the run. Valgrind is a very powerful tool for finding memory corruption, if the problem is memory corruption then valgrind will find it.

    Barry

> 
> 
> 
> 
> -----------------------------------------------
> Gig' em
> Jianchao Ge	
> Dept. of Geology and Geophysics
> Texas A&M University
> 
> 
> 
> 
> 
> On Dec 18, 2013, at 5:23 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> 
>> 
>> http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
>> 
>> On Dec 18, 2013, at 4:50 PM, Gavin Ge <jianchaoge at gmail.com> wrote:
>> 
>>> Hi All:
>>> 
>>> Hope everyone enjoy a nice holiday. I just got a problem with matsetvalues function when I mute the debugging option. A segmentation violation error jumps out when I set value for the very first element in the matrix. There is no problem for me to run the program when turning on the debugging option. I just want to tune this for better performance. Or is it better to turn on the debugging option? Could anybody help me with this? Thanks!
>>> 
>>> Regards,
>>> Gavin
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>