Inconsistent storage error during compilation #29
Comments
|
What version of macOS?
Wasn’t there a list of source files? If so, please provide them (you can paste a zip file into a comment here). If not - that’s another question.
It would be a start. Without it there is nothing that I can do. And a complete set of source files would be better. |
simonjwright
changed the title
|
Simon
Macos. Sequoia 15.2
The error message contained the following in addition:
Please include these source files with error report
Note that list may not be accurate in some cases,
so please double check that the problem can still
be reproduced with the set of files listed.
Consider also -gnatd.n switch (see debug.adb).
this is probably rather difficult since i ran into this every other build
today but not earlier.
i will be collecting all the files and upload but at this stage, this being
a sporadic issue, not too hopeful it can be replaced.
i will try to add the -gnatd.n switch to this unit and see if anything pops
up.
thanks for your considerations.
regards, Srini
…On Wed, Jan 29, 2025 at 10:32 AM Simon Wright ***@***.***> wrote:
What version of macOS?
Please include these source files with error report
Wasn’t there a list of source files? If so, please provide them (you can
paste a zip file into a comment here). If not - that’s another question.
I can provide the package "Critical_float" WHICH IS in a different project
- if it will help.
It would be a start. Without it there is *nothing* that I can do. And a
complete set of source files would be better.
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACZJWNBSDYEAYFWR7QCBSBL2NE3ERAVCNFSM6AAAAABWDWB5ECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRSG44DANJVGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
this project build successfully first. I created the zip file right after a failed build. Hope you are able to identify what is going on. Regards, Srini |
|
The first time I built it, it failed; thereafter, no problems. This morning, the first build failed: The second and third times, similar (not identical) results. Fourth time, compiled OK. Fifth time, error, this time at I ran I restored the source; occasional failures. I used
I’ve never seen the compiler fail like this, but then I have a compulsion to get clean compilations whenever possible, so I don’t get that many style warnings. If you really want to suppress all style warnings, |
|
Try building with e.g. |
|
Simon
Appreciate your analysis. I didnt even know where to start!
codemd (Code markdown) is the tool i built t produce code examples. Really
interesting these comment lines may have an impact. I use codemd
extensively in my entire "book" and not run into this before. Perhaps
because most of the time, I like to eliminate style related warnings
preferring to finally pretty print!
Excellent suggestions. WIll implement. Hopefully this will help me reach my
first major milestone.
Regards, Srini
…On Fri, Jan 31, 2025 at 4:44 AM Simon Wright ***@***.***> wrote:
Try building with e.g. alr build -- -gnaty-c (suppress the -gnatyc switch
(check comment format (two spaces))).
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACZJWNDZHJOCYTADV4R3EGL2NOD4ZAVCNFSM6AAAAABWDWB5ECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRXGUYTSNZZGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
"Analysis" is a big word for "poking at the problem until something seems to make it better"! I don’t know whether this is an aarch64 problem or applies to x86_64 as well .. it’s certainly still present in GCC 15.0.1. I’ll leave this issue open for the moment, in case I find something repeatable enough to raise a GCC bug report. |
|
See GCC PR 118782. |
|
Simon
Thanks for keeping me in the loop.
Regards, Srini
…On Fri, Feb 7, 2025 at 12:34 PM Simon Wright ***@***.***> wrote:
See GCC PR 118782 <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118782>.
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACZJWNCDKG6SAFLOCQHHOY32OTVCJAVCNFSM6AAAAABWDWB5ECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBTGU3DMMBVGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
One of my projects is not building - randomly.
Error message:
Compile
[Ada] cvars.adb
+===========================GNAT BUG DETECTED==============================+
| 14.2.0 (aarch64-apple-darwin23) Storage_Error stack overflow |
| Error detected at cvars.adb:9:5 |
| Compiling /Users/rajasrinivasan/Prj/GitLab/toolkit/examples/cvar/src/cvars.adb|
| Please submit a bug report; see https://gcc.gnu.org/bugs/ . |
| Use a subject line meaningful to you and us to track the bug. |
| Include the entire contents of this bug box in the report. |
| Include the exact command that you entered. |
| Also include sources listed below. |
+==========================================================================+
Please include these source files with error report
identical files will fail randomly. The file - package and spec look like this:
--codemd: begin segment=Variables caption=declaration
with critical_float ;
package cvars is
tempSetpoint : critical_float.Variable_Type ;
pressureSetpoint : critical_float.Variable_Type ;
function allocator( secondary : boolean ) return access Float ;
end cvars ;
--codemd: end
-- codemd: begin segment=Implement caption=Implementation
package body cvars is
function allocator( secondary : boolean ) return access Float is
begin
return new Float ;
end allocator ;
begin
critical_float.SetAllocators( allocator'access );
end cvars ;
--codemd: end
I can provide the package "Critical_float" WHICH IS in a different project - if it will help.
Project builds on linux VMs and Docker - reliably. Hence this "ISSUE"
any clues?
Srini
The text was updated successfully, but these errors were encountered: