From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506; InfoPath.2) Description of problem: When creating one snackScreen after another continuously, I reliably get a segfault after 168 runs of the attached code(try.py). However, using try2.py, I was able to get 500 runs with no problems. This bug was quite obscure because it did not show up immediately. In this example it does take a large number of runs for the bug to surface. Perhaps a check should be made to check if a helpline already exists before letting the caller pushHelpLine. Version-Release number of selected component (if applicable): newt-0.52.2-9 How reproducible: Always Steps to Reproduce: 1.Run try.py 2.Notice that it segfaults after 167 runs 3.Run try2.py 4.No segfaults. Actual Results: Expected Results: Additional info:
Created attachment 154624 [details] Code that causes segfault.
Created attachment 154625 [details] Code that solves the problem.
Thanks for the report. SnackScreen with each initialization calls pushHelpLine to have the default help string, the stack keeps growing and there is no check for overflow.
Fixed in upstream CVS, will be in the next release.
Fixed in newt-0.52.7-1.fc8.
newt-0.52.7-1.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
newt-0.52.7-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.