I can get a core file,but it is not very informative, at least to me. The backtrace is only 3 entries, in hex, then a message duplicate entries,possible stack corruption. This is what I got last night, need to try again after the clone -mob. Anything I can do to get symbolic or additional info into the core file when the seg fault occurs?
Regards, Jerry On Jan 27, 2013 8:13 AM, "Thomas Preud'homme" <[email protected]> wrote: > Le dimanche 27 janvier 2013 14:07:19, vous avez écrit : > > Thank you. > > > > I will clone the repository again with -mob and test again. > > Thanks. I appreciate any testing since I made a significant (not in terms > of > line of code but in terms of possible regressions) change in the arm code > yesterday. It allows __builtin_frame_address to work properly so I wanted > this > change in. If you notice anything, I'll revert it and keep it for after the > release. I'll spend my evening trying to fix the random segfault by trying > to > have a coredump and release after that. If I don't have an idea of the > problem > before tomorrow, I'll release anyway (I think the bug was already there > since > long time). Else, I'll allow myself 1-2 more days to fix it. > > > > > Regards, > > Best regards, > > > > > Jerry > > Thomas >
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
