Up to top level
AO15   AO16   AO17   AO18   AO19   Backgrounds   Calibration   Conference   Data   Docs   EPICMOS   EPICpn   Feedback   Gallery   Misc   OM   Pending   PhD_Theses   Publications   RGS   RadMonitor   SAS_Hardware   SAS_WS   SASv16.0   SASv16.0_Installation   SASv16.1   SASv16.1_Installation   SASv17.0   SASv17.0_Installation   SASv18.0   SASv18.0_Installation   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest

Viewing SASv17.0_Installation/84903
Full headers

From: Roderick Johnstone <rmj@ast.cam.ac.uk>
Subject: Re: Memory allocation errors in hkgtigen in Fedora 28 and 30 beta
Compose reply
Download message
Move To:
0 replies:
0 followups:

Private message: yes  no

Notes:

Notification:


Subject: Re: Memory allocation errors in hkgtigen in Fedora 28 and 30 beta
To: Pedro Rodriguez <xmmhelp@sciops.esa.int>
From: Roderick Johnstone <rmj@ast.cam.ac.uk>
Date: Mon, 29 Apr 2019 16:21:02 +0100
Hi Pedro

Thanks for the update. It seems that the work around is good enough to 
be going on with. Hopefully the analysts can come up with a permanent 
solution in due course.

Roderick

On 29/04/2019 16:38, Pedro Rodriguez wrote:
> Hi,
> 
> thank you very much for the detailed analysis made on the fatal error
> issued by rgsproc.
> 
> SAS analysts have been able to identify the task hkgtigen as the one
responsible
> 
> for the fatal error. The error is issued also when processing EPIC pn and
MOS
> data and not only associated to RGS. Furthermore, the problem is persistent
in
> the
> forthcoming SAS18.0 release.
> 
> As mentioned in your email, the error occurs for most recent versions of
> glibc library but apparently there is nothing in their release notes that
> justify it. The SAS analysts are debugging the code as well as re-checking
> the library release notes and SAS compilation options to understand
properly
> the
> origin of the problem and, eventually, fix it.
> 
> Meanwhile, for future questions in our helpdesk about the same or similar
issue
> we will refer to the workaround in your email to set MALLOC_CHECK to 1 or
2.
> 
> If by the time of SAS18.0 is released we have not found a solution to the
> problem we are considering to add a specific entry in our SAS Watchout
page.
> 
> Thanks again,
> 
> Pedro

-- 
Roderick Johnstone                          Email: rmj@ast.cam.ac.uk
Institute of Astronomy                      Phone: +44 (0)1223 766656
Madingley Road, Cambridge CB3 0HA, UK       Mobile:+44 (0)7989 809095

Up to top level
AO15   AO16   AO17   AO18   AO19   Backgrounds   Calibration   Conference   Data   Docs   EPICMOS   EPICpn   Feedback   Gallery   Misc   OM   Pending   PhD_Theses   Publications   RGS   RadMonitor   SAS_Hardware   SAS_WS   SASv16.0   SASv16.0_Installation   SASv16.1   SASv16.1_Installation   SASv17.0   SASv17.0_Installation   SASv18.0   SASv18.0_Installation   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest


Please make your (short) question the subject of your request!


Web interface using JitterBug ... back to the XMM home page