Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Petsc error after implicit time stepping in 1D acoustics run with nose #22

Closed
mparsani opened this issue Jun 2, 2011 · 2 comments
Closed
Assignees

Comments

@mparsani
Copy link
Contributor

mparsani commented Jun 2, 2011

FAILED (errors=1)
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/petsc-as/documentation/faq.html#valgrind[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[0]PETSC ERROR: likely location of problem given in stack below
[0]PETSC ERROR: --------------------- Stack Frames ------------------------------------
[0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available,
[0]PETSC ERROR: INSTEAD the line number of the start of the function
[0]PETSC ERROR: is given.
application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0
[unset]: aborting job:
application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0

@ghost ghost assigned ahmadia Jun 2, 2011
@ahmadia
Copy link
Member

ahmadia commented Jun 2, 2011

I am going to try and reproduce this on my local workstation and report back when I have a more clear idea of where the problem is.

@mparsani
Copy link
Contributor Author

This issue is not solved. However, we are going to abandon the implicit TS implemented in PETSc. We want to implement our own time integrators. In future, implicit TS in PETSc could be reconsidered, e.g. if we want to compare the CPU time of the two approaches (TS in PETSc are written in C; in PetClaw in Python).
Thus I close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants