Opened 13 months ago

Closed 5 months ago

#30868 closed defect (invalid)

sage fails to start on Fedora 32 after the recent update to Python 3.8

Reported by: gh-AndrewLyasoff Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: build Keywords:
Cc: Merged in:
Authors: Reviewers: Samuel Lelièvre
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by gh-AndrewLyasoff)

The crash report is attached. The installation is from the latest Fedora 32 package (sage 9.0).

Attachments (1)

Sage_crash_report.txt (50.8 KB) - added by gh-AndrewLyasoff 13 months ago.

Download all attachments as: .zip

Change History (7)

Changed 13 months ago by gh-AndrewLyasoff

comment:1 Changed 13 months ago by gh-AndrewLyasoff

  • Description modified (diff)

comment:2 Changed 13 months ago by mkoeppe

  • Milestone changed from sage-9.3 to sage-duplicate/invalid/wontfix
  • Status changed from new to needs_review

Report Fedora packaging bugs to Fedora.

comment:3 Changed 13 months ago by gh-jamesjer

For the record, this started happening when giac was updated from version 1.6.0-7 to version 1.6.0-25. The way giac initializes pari was changed. Sagemath starts up and initializes cypari2, which stores the value of avma. Later, giac is loaded. It initializes pari a second time, creating an entirely new stack and a new value of avma. When cypari2 is next used, it tries to use values on the old stack, but they are not valid stack slots because giac made a new pari stack.

I am going to try enabling TLS support in pari to see if that is sufficient. That way, cypari2 and giac threads can use different pari stacks, at the cost of consuming more memory.

comment:4 Changed 13 months ago by mkoeppe

This is probably best discussed in #30537, our giac 1.6 upgrade ticket

comment:5 Changed 11 months ago by slelievre

  • Component changed from PLEASE CHANGE to build
  • Reviewers set to Samuel Lelièvre
  • Status changed from needs_review to positive_review

comment:6 Changed 5 months ago by mkoeppe

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