{"id":583,"date":"2008-08-06T22:18:30","date_gmt":"2008-08-07T05:18:30","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/gcc-heisenbug\/"},"modified":"2008-08-06T22:18:30","modified_gmt":"2008-08-07T05:18:30","slug":"gcc-heisenbug","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/gcc-heisenbug\/","title":{"rendered":"gcc Heisenbug"},"content":{"rendered":"

In my last post<\/a>, when I endeavored to enter a gcc bug regarding the internal compiler error when compiling FFmpeg<\/a> on PPC, I could not reproduce the problem when I separated the compiler from ccache<\/a>. I finally got, umm, lucky<\/em> when the FFmpeg tree got into a state when the compiler threw the error without ccache’s involvement.<\/p>\n

So I followed the steps outlined for a proper, useful bug reporting page, as listed on gcc’s bug reporting page<\/a>. I added the -save-temps option to the command line…<\/p>\n

…and the compiler no longer crashes. <\/em><\/p>\n

The term here is Heisenbug<\/em><\/a>.<\/p>\n

Anyway, I have finally entered a bug<\/a> in order to start tracking this issue. <\/p>\n","protected":false},"excerpt":{"rendered":"

In my last post, when I endeavored to enter a gcc bug regarding the internal compiler error when compiling FFmpeg on PPC, I could not reproduce the problem when I separated the compiler from ccache. I finally got, umm, lucky when the FFmpeg tree got into a state when the compiler threw the error without […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[101],"tags":[],"class_list":["post-583","post","type-post","status-publish","format-standard","hentry","category-fate-server"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t