File: PetscClearMalloc.html

package info (click to toggle)
petsc 2.1.3-1.woody.1
  • links: PTS
  • area: main
  • in suites: woody
  • size: 70,272 kB
  • ctags: 310,869
  • sloc: ansic: 257,275; sh: 9,870; makefile: 7,622; fortran: 6,211; cpp: 1,026; python: 416; csh: 41; asm: 9
file content (29 lines) | stat: -rw-r--r-- 1,110 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="DOCTEXT">
<TITLE>PetscClearMalloc</TITLE>
</HEAD>
<BODY BGCOLOR="FFFFFF">
<A NAME="PetscClearMalloc"><H1>PetscClearMalloc</H1></A>
Resets the routines used to do mallocs and frees to the  defaults. 
<H3><FONT COLOR="#CC3333">Synopsis</FONT></H3>
<PRE>
#include "petsc.h"   
int PetscClearMalloc(void)
</PRE>
Not Collective
<P>

<P>
<H3><FONT COLOR="#CC3333">Notes</FONT></H3>
In general one should never run a PETSc program with different malloc() and
free() settings for different parts; this is because one NEVER wants to
free() an address that was malloced by a different memory management system
<P>
<P><B><P><B><FONT COLOR="#CC3333">Level:</FONT></B>developer
<BR><FONT COLOR="#CC3333">Location:</FONT></B><A HREF="../../../src/sys/src/memory/mal.c.html#PetscClearMalloc">src/sys/src/memory/mal.c</A>
<BR><A HREF="./index.html">Index of all Sys routines</A>
<BR><A HREF="../../index.html">Table of Contents for all manual pages</A>
<BR><A HREF="../singleindex.html">Index of all manual pages</A>
</BODY></HTML>