{"thread":{"id":"32792","subject":"Re: Re: Re: Segmentation fault with latest git (070c57df)","startedAt":"2013-01-31T08:07:16Z","lastAt":"2013-01-31T08:07:16Z","messageCount":1,"participants":["허종만"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"208347","messageId":"6083817.360021359619635900.JavaMail.weblogic@epv6ml01","threadId":"32792","inReplyTo":null,"subject":"Re: Re: Re: Segmentation fault with latest git (070c57df)","fromName":"허종만","fromEmail":"jongman.heo@samsung.com","sentAt":"2013-01-31T08:07:16Z","receivedAt":"2013-01-31T08:07:16Z","isPatch":false,"sender":{"key":"jongman.heo@samsung.com","avatar":null},"body":"\n> It's almost like the compiler is getting the initializer wrong. It's a\n> long shot, but I wonder if the presence of the bitfield could be\n> triggering a compiler bug (or there is a subtle C rule about bitfield\n> initializations that I do not know). Just for the sake of my sanity,\n> what does the following program output for you?\n\nHi, \n\njust \"cmp is 0\"  is printed.\n\n$ gcc --version\ngcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48)\nCopyright (C) 2006 Free Software Foundation, Inc.\nThis is free software; see the source for copying conditions.  There is NO\nwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n\n\nBest regards,\nJongman Heo."}]}