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

do something about the pari overflow test #1595

Closed
williamstein opened this issue Dec 24, 2007 · 7 comments
Closed

do something about the pari overflow test #1595

williamstein opened this issue Dec 24, 2007 · 7 comments

Comments

@williamstein
Copy link
Contributor

This disturbs people:

sage -t  devel/sage-main/sage/libs/pari/gen.pyx             python(85565) malloc: *** mmap(size=4096000000) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug

This would disturb people less:

[[The following doctest contains an intentional memory error.]]
sage -t  devel/sage-main/sage/libs/pari/gen.pyx             python(85565) malloc: *** mmap(size=4096000000) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug

Component: doctest coverage

Issue created by migration from https://trac.sagemath.org/ticket/1595

@williamstein williamstein added this to the sage-3.4.2 milestone Dec 24, 2007
@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Dec 25, 2007

comment:1

The issue has been added to the FAQ. It might be easiest to direct stderr to some file. That way people should never see the offending message.

Cheers,

Michael

@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Feb 8, 2009

comment:3

On OSX 10.5 64 bit, FreeBSD 7 as well as Solaris Sparc this overflow test leads to a segfault/failed test. I am not sure what to do with this test since the fact that it worked purely depends on the OS behavior for large allocs.

Maybe making it "optional -- large" or "optional -- $SOME_OS_LIST" would be a way out of this. Anyway, there seems to be no reliable way to test the allocation of huge amounts of memory and expect the Sage session to survive.

Cheers,

Michael

@williamstein
Copy link
Contributor Author

comment:4

Attachment: gen.patch.gz

@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Apr 8, 2009

comment:5

Positive review.

Cheers,

Michael

@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Apr 8, 2009

comment:6

Oops, change the summary, too.

Cheers,

Michael

@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Apr 8, 2009

comment:7

Ooops, this patch needs to be rebased for 3.4.1.rc1 - new patch coming up in the morning.

Cheers,

Michael

@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Apr 9, 2009

comment:8

Attachment: trac_1595-rebase.patch.gz

Merged trac_1595-rebase.patch in Sage 3.4.1.rc2.

Cheers,

Michael

@sagetrac-mabshoff sagetrac-mabshoff mannequin closed this as completed Apr 9, 2009
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