-
Notifications
You must be signed in to change notification settings - Fork 50
Code Errors (two) #117
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
Comments
Can't reproduce segfault 1 Segfault 2 is because Page 13 has no last label entry and my The line with the segfault: Line 73 in 4404676
f->label.Set(PhraseData[idx].text);
|
I did some more digging for the second segfault: I recommend to update the PhraseData for this page 13 by removing the following line: Line 243 in 4404676
The Lines 297 to 307 in 4404676
|
Page 13 of 16 (page index 12) has a reference to FamilyName[31], which is a char* pointer initialized with `NULL`. When this `nullptr` is passed to `Str::Set(const char *)` this results in a Segmentation fault. Fixes: ViewTouch#117
reopen for the first segfault in "Receipts Balance" not yet fixed |
Thanks for the prompt code repair, NeroBurner ! I made a clean start of the /usr/viewtouch/dat directory and was able to determine that the first of the two Code Errors I made mention of here seems to be a file corruption issue. I intend to issue a new microSD image soon to rectify this problem. |
Two code errors which cause a program exit have been reported. To see them, Logon as Editor (User ID 42) > Start > Manager's Gateway
First code error: > Reports > Receipts Balance
The next page which should appear is System Page -62, Accountant's Report. Sometimes the program exits before System Page -62 displays and sometimes the program exits after System Page -62 displays but when any button on System Page -62 is selected.
Second code error: > Configuration > Customize Job Titles, Families, Phrases
The program exits when Page 13 (of 16) is selected.
Hopefully it's useful to mention that both of these program exits have shown themselves and were fixed in the past.
The text was updated successfully, but these errors were encountered: