Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation fault (core dumped) #106

Open
rruhle opened this issue Oct 1, 2022 · 5 comments
Open

Segmentation fault (core dumped) #106

rruhle opened this issue Oct 1, 2022 · 5 comments

Comments

@rruhle
Copy link

rruhle commented Oct 1, 2022

123 crash returns to terminal with "Segmentation fault (core dumped)" at command line.

Fault repeats reliably when macro allowed to run without interruption.

Macro STEP function avoided crash by delaying steps, and macro finished normally.

Macro STEP not visible at status line with 123.elf, so exact macro call that triggers fault is unknown

@taviso
Copy link
Owner

taviso commented Oct 1, 2022

Thank you, do you have a worksheet that demonstrates the crash?

If I can reproduce it I can probably fix it!

@rruhle
Copy link
Author

rruhle commented Oct 2, 2022

After your worksheet copy renamed remote-file names to prevent over-writing newer records fault would not repeat.

Perhaps another app locked a file during 123 macro calls to remote files? Will keep monitoring.

Tried Ctrl-C to break macro STEP near fault location, but only found {FOR counter..} loop with no storage calls.

Fault won't replicate with original backup worksheet, after accounting records were updated later today.

@rruhle
Copy link
Author

rruhle commented Dec 12, 2022

Using 123 v2 Maco function {For counter..} with {forbreak}, at end of long subroutine loop in 123.elf, may have fixed error.

My novice attempt at macros originally developed on Lotus 123 for DOS worked, but perhaps should have crashed long before 123.elf spit them out, with "Segmentation fault (core dumped)".

If original spreadsheet macro are replicated with this error, I will post the file here for examination.

@rruhle
Copy link
Author

rruhle commented Jan 1, 2023

Spreadsheet file sent to Taviso

@taviso
Copy link
Owner

taviso commented Jan 3, 2023

I don't see it, could you send it again? You can mail it to [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants