Closed marcomaggi closed 11 years ago
a little more information about this isse: the stack of core file: Core was generated by `../src/vicare -b ../../scheme/vicare.boot.8.prebuilt ../../scheme/makefile.sps'. Program terminated with signal 11, Segmentation fault.
(gdb) bt
(gdb) quit
mean while, the kernel report general protection error chaos@felucia:~/src/vicare/:build/scheme$ dmesg [13849.122989] vicare[15609] general protection ip:7f49a326e06e sp:7f49a4050ff8 error:0
Have you tried "git bisect" to find the commit that broke it?
Who is your "you"? :-) The only way to identify the commit that broke it is: use a 64-bit computer, checkout a commit, build a new boot image, try to run it. "git bisect" helps with the 3 latter steps, but I do not own a 64-bit computer. If someone wants to contribute time to do this search, he is welcome.
I am dealing with it On Feb 12, 2013 4:37 PM, "Marco Maggi" notifications@github.com wrote:
Who is your "you"? :-) The only way to identify the commit that broke it is: use a 64-bit computer, checkout a commit, build a new boot image, try to run it. "git bisect" helps with the 3 latter steps, but I do not own a 64-bit computer. If someone wants to contribute time to do this search, he is welcome.
— Reply to this email directly or view it on GitHubhttps://github.com/marcomaggi/vicare/issues/39#issuecomment-13422729.
@ChaoeEternal: have you verified that the boot image in the latest release is still broken?
Yes, 0.2d21 is still broken On Feb 13, 2013 3:11 AM, "Marco Maggi" notifications@github.com wrote:
@ChaoeEternal: have you verified that the boot image in the latest release is still broken?
— Reply to this email directly or view it on GitHubhttps://github.com/marcomaggi/vicare/issues/39#issuecomment-13449847.
chaos@felucia:~/src/vicare$ git bisect log git bisect start
git bisect bad 44dd037d5d03e51d7918a6c4df94c40f1038dea5
git bisect good e14cda2b4fa68b5d1ceb500288b6f49f7e0fbc61
git bisect good 61191dd87ae26a13ac5a71bfae32121b3771ee6a
git bisect bad 1c83b5c5ac6010f8575146c180fccededecc4a56
git bisect good 00392bcd1ba7c48a53523571de9a17e30ce5c5f4
git bisect bad 2b4ede94890809d5736fbbba5e789a42e10b61ac
git bisect bad 6f616ae4fd04e5a05ceebad5eafc422a48cac929
git bisect bad da030b718242cd93300716914821fcd8e22bf5a5
git bisect bad a5774d325ac2603b65f28d2ffd69adc154a548d1
git bisect bad 3909eb3d56caf543605b1f5aa9aa0547ac4784f2
git bisect good 5a5bccd6f5214d8868eb55a0df31d15f49bd1eb5
git bisect good 34f08a991bde981b9f17594826265df9fc2a8d1c
Thanks!!! I will upload soon a test release with a fix.
It should be fixed now in the devel branch, commit e0107d37acc6f8cbe6fd4a9b542883e01ddc7481.
It is not fixed. Many bugs shown by the test suite. Development of 64-bit support goes on on the branch "support-for-64-bit".
Should be fixed in the head of the devel branch.
Great job!!!
On Sat, Jun 29, 2013 at 9:17 PM, Marco Maggi notifications@github.comwrote:
Should be fixed in the head of the devel branch.
— Reply to this email directly or view it on GitHubhttps://github.com/marcomaggi/vicare/issues/39#issuecomment-20229619 .
The code generates invalid boot images for 64-bit platforms.