BAD TERMINATION when output

[Shen-Zhen-Xiong]

Describe the bug

case_Cr3Te4.tar.gz
There are some core dumps while output the results. the error message is:

terminate called after throwing an instance of 'std::out_of_range'
what(): map::at

Expected behavior

No response

To Reproduce

No response

Environment

No response

Additional Context

No response

Task list for Issue attackers (only for developers)

• Verify the issue is not a duplicate.
• Describe the bug.
• Steps to reproduce.
• Expected behavior.
• Error message.
• Environment details.
• Additional context.
• Assign a priority level (low, medium, high, urgent).
• Assign the issue to a team member.
• Label the issue with relevant tags.
• Identify possible related issues.
• Create a unit test or automated test to reproduce the bug (if applicable).
• Fix the bug.
• Test the fix.
• Update documentation (if necessary).
• Close the issue and inform the reporter (if applicable).

[mohanchen]

We will take a closer look

[dyzheng]

@Shen-Zhen-Xiong I think it maybe caused by one of these three settings:

out_mul                         1
out_mat_hs2                    1
out_mat_t                      1
out_mat_r                      1

can you check that?

[Shen-Zhen-Xiong]

@dyzheng Thx, I will try to test these settings

[Shen-Zhen-Xiong]

@dyzheng while out_mat_t 1, it is error

[DirtRain]

I used abacus-v3.9.0 compiled with oneapi-2024.0.1, and I found that setting out_mul 1 would also cause a segmentation fault at the end of the calculation.