merge from 31

Hg-commit: 2aec9ed184d1b152621814295b230e54660ccbf0

Merge

Hg-commit: 02178143ddd3e6d6cc6a3a3261c8b862015885b1

added AMSBean, amsoptions.java ams viewer

Hg-commit: 111ac237c359799b5be34e07489680f7acbf029c

Merge

Hg-commit: 3d6e115ed50e0a91aeb25dbd4b36559e2e6d6008

some fixes for dynamic libraries load including adding characteristic, fixes for multiple libraries
removed Usage Statistics from webpages since had no useful information

Hg-commit: 60bc2b7630581287

some fixes for dynamic libraries load including adding characteristic, fixes for multiple libraries
removed Usage Statistics from webpages since had no useful information

Hg-commit: 60bc2b76305812878b4dd93b664f25326281ac25

show more ...

merge

Hg-commit: 05d5009003ecfc80d5043a07199af616ee7c2323

changed PetscGetVersion() to not use unneeded and dangerous PetscStrcat()
added missing \n in PETSc help message
added initial xcode project that builds a simple iphone app

Hg-commit: 66d7e91cc737e8

changed PetscGetVersion() to not use unneeded and dangerous PetscStrcat()
added missing \n in PETSc help message
added initial xcode project that builds a simple iphone app

Hg-commit: 66d7e91cc737e8a060fee138585f89c5bc417239

show more ...

Merge

Hg-commit: 091935e9281c6e900c1e00205f59cde73745cb0d

On May 13, 2010, at 10:48 AM, Jed Brown wrote:

I'm concerned by the following which appears in
PetscAttachDebuggerErrorHandler() and Petsc_MPI_DebuggerOnError():

ierr = PetscAttachDebugger();
if

On May 13, 2010, at 10:48 AM, Jed Brown wrote:

I'm concerned by the following which appears in
PetscAttachDebuggerErrorHandler() and Petsc_MPI_DebuggerOnError():

ierr = PetscAttachDebugger();
if (ierr) { /* hopeless so get out */
MPI_Finalize();
exit(*flag);
}

Since the error handler is not guaranteed to be called collectively, it
seems completely unreasonable to call a collective function, especially
not one with broader scope than PETSC_COMM_WORLD. It seems to me that
the hopeless case should instead call MPI_Abort() on the relevant
communicator.

You are probably right; this code fragment is so old it may have been written before I knew what MPI_Abort() was. I am changing it.


Similarly, why does Petsc_MPI_AbortOnError() call abort()
instead of MPI_Abort()?

I think this is clearly documented in the comment above it. Here is the comment:

This is so MPI errors in the debugger will leave all the stack
frames. The default abort cleans up and exits.

You use this error handler if you are running in the debugger (for example with -start_in_debugger). If you call MPI_Abort() it cleans up and you get no useful stack information in the debugger. I will change the comment to:

This is so MPI errors in the debugger will leave all the stack
frames. The default MP_Abort() cleans up and exits thus providing no useful information
in the debugger hence we call abort() instead of MPI_Abort().

Is it clear now, or am I missing something?

Barry

Hg-commit: 4663027817c3c85b7bd6d5229eb182ec49e8cf67

show more ...

a few reformating of SETERRQX() and replacing of PETSC_COMM_SELF with more appropriate communicator

Hg-commit: 49045fdc9861811799c249237e36dc69203313e1

removed unneeded { around SETERRQX() calls}

Hg-commit: d55148dbbe8a10f500a7e181b91ba166aec6f665

added MPI_Comm as first argument to PetscError() and SETERRQX()

Hg-commit: fe5a2ff050abc00ca2c2979c0af22b117b62874e

Parens on conditional

Hg-commit: dc051888f025ca8cc9d41064f5f34d936e4e0277

Merge

Hg-commit: 1f5ce9b1fa7762a7d57e66fe241c05a915d43e19

Merge.

Hg-commit: bfe14fc1c10a348d95f62b10a73037a938b09cb6

commit after merge

Hg-commit: f3908c33ff77348d21c6f59a4d399376069e9745

Included petscfwk.h in petscsys.h.

Hg-commit: beb62898e791b754ec31f1e2cf7fd02b6220ecba

some code cleanup and further work on DMMG version 2

Hg-commit: 896f032fd4a8a52f74fc4b043ca1a9059a613c52

ScatterMode value manual pages belong in petscvec.h not petscsys.h

Hg-commit: 7cf3281904e4ccabdd8d2361927a5819507ce637

general cleanup of petscsys.h
removed PetscStrfree() since PetscFree() does the same thing

Hg-commit: 383ece197d31b92016b12ff3a62a2e744f8d981d

systematically changed use of phrase of ./config/configure.py to ./configure to have one consistent (and standardish) way of refering to it. Having two ways of refering to the same thing is confusing

systematically changed use of phrase of ./config/configure.py to ./configure to have one consistent (and standardish) way of refering to it. Having two ways of refering to the same thing is confusing and unneccesary

Hg-commit: fcd327f3f4fcb82c63cd1afe8da55ad84e8250f3

show more ...

commit after merge

Hg-commit: b848d8d6cf58331964a5f3f4e77524f4c1163686

fix incomplete PetscObjectGetClassId() change

Hg-commit: 32d2521a0f5fd7aef43e92363c4bac1b775371df

Merge.

Hg-commit: 96dff560e9caff2ee6539fb4c50e92b67324e0b0

commit after pull of manual pages patches for 3.1

Hg-commit: fdda79b9b0cfa271aff815250a8f6761d22b5ee8