Ticket #12654 (closed defect: duplicate)

Opened 15 months ago

Last modified 12 months ago

polybori crash (Linux)

Reported by: cbwolf Owned by: tbd
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: packages: standard Keywords: polybori multivariate quadratic polynomials
Cc: AlexanderDreyer Work issues:
Report Upstream: Fixed upstream, in a later stable release. Reviewers: Alexander Dreyer
Authors: Merged in:
Dependencies: Stopgaps:

Description (last modified by AlexanderDreyer) (diff)

Hello,

I think I found a bug in Sage 4.8, more specifically in polybori. Polybori terminates with a "segmentation fault". I have attached the input (sparse polynomials) and the output. I can reproduce the error with this specific input.

For smaller instances (i.e. less variables, less equations), the programme runs fine and the output is correct.

The machine has about 256 GB RAM, uses an AMD Opteron(TM) Processor 6276 @ 2.3 GHz and runs under Linux 2.6.32-220.2.1.el6.x86_64.

If you need any more info: Please drop me a line!

Best, Christopher

Duplicate of #11575.

Attachments

ticketMinimal.sage Download (583.3 KB) - added by cbwolf 15 months ago.
Minimal Input that makes polybori crash
testOut.txt Download (6.0 KB) - added by cbwolf 15 months ago.
Output of the test file
testError.txt Download (292 bytes) - added by cbwolf 15 months ago.
Error message of the test file

Change History

Changed 15 months ago by cbwolf

Minimal Input that makes polybori crash

Changed 15 months ago by cbwolf

Output of the test file

Changed 15 months ago by cbwolf

Error message of the test file

comment:1 follow-up: ↓ 2 Changed 15 months ago by AlexanderDreyer

  • Cc AlexanderDreyer added
  • Keywords polybori added; polibori removed
  • Status changed from new to needs_info
  • Report Upstream changed from N/A to Fixed upstream, in a later stable release.

It seems that this is fixed by #12655 or #12656 (for sage-5.0alpha). Can you verify this?

comment:2 in reply to: ↑ 1 Changed 15 months ago by AlexanderDreyer

Replying to AlexanderDreyer:

It seems that this is fixed by #12655 or #12656 (for sage-5.0alpha). Can you verify this?

Maybe #11575 already fixed that (still it works only for sage-5.0).

comment:3 Changed 15 months ago by cbwolf

Thanks for pointing this out!

Yes, the bug is gone with sage-5.0beta_a11.

Best, Christopher

comment:4 Changed 12 months ago by AlexanderDreyer

  • Status changed from needs_info to needs_review

Duplicate of #11575.

comment:5 Changed 12 months ago by AlexanderDreyer

  • Status changed from needs_review to positive_review
  • Description modified (diff)

Abusing "positive review", because I cannot close it.

comment:6 Changed 12 months ago by jdemeyer

  • Reviewers set to Alexander Dreyer
  • Milestone changed from sage-5.1 to sage-duplicate/invalid/wontfix

In such cases, you should set the milestone to "sage-duplicate/invalid/wontfix".

comment:7 Changed 12 months ago by jdemeyer

  • Status changed from positive_review to closed
  • Resolution set to duplicate
Note: See TracTickets for help on using tickets.