Re: profiling PETSc code

To: petsc-users@xxxxxxxxxxx
Subject: Re: profiling PETSc code
From: "Matthew Knepley" <knepley@xxxxxxxxx>
Date: Tue, 1 Aug 2006 19:28:08 -0500
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qTySKD1Dwfv9rPHAE0S6o7xHbGG6Tut2txHFqoKp8cQi6g/9SbaTrKqlODS5b1iEhlZj5Y09PKDZRdu7iRI7EFIgZYhrNT90WqigUETncHCmDz8nqZObdKaBq9ZkO2vJk2Tz52uJ8Oju7jB3mBglDXle9dp4OGJgQOkRG9BxkGA=
In-reply-to: <200608011807.29007.mafunk@nmsu.edu>
References: <200608011545.26224.mafunk@nmsu.edu> <a9f269830608011536v12fb4457l31e3d363a666a893@mail.gmail.com> <200608011749.48651.mafunk@nmsu.edu> <200608011807.29007.mafunk@nmsu.edu>
Reply-to: petsc-users@xxxxxxxxxxx
Sender: owner-petsc-users@xxxxxxxxxxx

On 8/1/06, Matt Funk <mafunk@xxxxxxxx> wrote:

Actually the errors occur on my calls to a PETSc functions after calling
PETSCInitialize.


Yes, it is the error I pointed out in the last message.

  Matt

mat

--
"Failure has a thousand explanations. Success doesn't need one" -- Sir
Alec Guiness

References:
- profiling PETSc code
  - From: Matt Funk
- Re: profiling PETSc code
  - From: Matthew Knepley
- Re: profiling PETSc code
  - From: Matt Funk
- Re: profiling PETSc code
  - From: Matt Funk