Group Abstract Group Abstract

Message Boards Message Boards

Why does the WolframKernel exit on OS X without a trace during Integrate?

Janos Lobb
Posted 8 years ago
Attachments:
POSTED BY: Janos Lobb
5 Replies
Sort By:

A notebook or .m file with the input would be more useful in terms of diagnosing the issue.
POSTED BY: Daniel Lichtblau
Janos Lobb
Janos Lobb
Posted 8 years ago

Thanks Mr. Lichtblau. Next Monday I can upload an OS X panic file I sent to Apple if that helps catching the bug.
POSTED BY: Janos Lobb
Janos Lobb
Janos Lobb
Posted 8 years ago

Should not be an option for the user to disable all TimeConstrained, especially if the user expecting an Integrate that lasts for hours or even overnight ?
POSTED BY: Janos Lobb

Variations of that have been discussed in past but never implemented.Perhaps just as well, since many integrals with parameters, and even some without, would just wander off to Never-never Land. I should add that this is more or less incidental to the crash issue, which is just a bug (at least if the cause is what I suspect and described).
POSTED BY: Daniel Lichtblau

Might be a kernel problem involving a failure to properly deal with the result of an internal interrupt. Integrate uses TimeConstrained in many places to avoid hanging when e.g. trying to sort out provisos (conditions for which one has convergence, or a result might hold), attempting to take limits, etc.
POSTED BY: Daniel Lichtblau
Reply to this discussion
Community posts can be styled and formatted using the Markdown syntax.
Tag limit exceeded
Note: Only the first five people you tag will receive an email notification; the other tagged names will appear as links to their profiles.
Reply Preview
Attachments
Remove
or Discard