Re: speed-dreams-2.4.2: How to determine the cause of a SIGSEGV signal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



What is the recipe to reproduce the crash? I see no crash running speeddreams-2.4.2 from rawhide on a fresh Fedora 42: click anywhere
in the window with 3 cars, Quit, confirm.  Also works with valgrind.

It seems to me that many of the "???" return addresses probably are
on pages that have been unmapped.  I have written a short tool (shared
library dynamically loaded into the process at debug time) that looks up
addresses in /proc/self/exe:  https://bitwagon.com/findpage.c

Using findpage at the time of the SIGSEGV, then I believe that many of
the "???" addresses will be "not found" in the running page mappings.
If so, then sprinkle some breakpoints into the code, "(gdb) run" again
under the same gdb session to get the same mappings [not re-randomized]
and check the addresses that were "???" in the first "(gdb) run"
to see when their pages might have become unmapped.


--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux