Chromium 19 dumps core on 9.0-RELEASE (i386)

[George Liaskos]

On Fri, Jun 8, 2012 at 4:06 PM, David P. Caldwell
<david at code.davidpcaldwell.com> wrote:
> I don't know much about native libraries -- what would be the possible
> causes of a build with debugging symbols being functional but a build
> without them crashing? Is that a compiler bug?
>
> I built with gcc, if it's relevant.
>
> -- David.
>
> On Fri, Jun 8, 2012 at 8:11 AM, George Liaskos <geo.liaskos at gmail.com> wrote:
>> On Fri, Jun 8, 2012 at 2:46 PM, David P. Caldwell
>> <david at code.davidpcaldwell.com> wrote:
>>> On Fri, Jun 8, 2012 at 3:46 AM, George Liaskos <geo.liaskos at gmail.com> wrote:
>>>> On Thu, Jun 7, 2012 at 9:04 AM, Baptiste Daroussin <bapt at freebsd.org> wrote:
>>>>> On Wed, Jun 06, 2012 at 07:34:05PM -0400, David P. Caldwell wrote:
>>>>>> I built the latest Chromium 19 by building against the 9.0-RELEASE
>>>>>> *packages*. I did not want to update all my ports and incur the
>>>>>> various library problems that resulted the last time I tried that. I
>>>>>> may try it next.
>>>>>>
>>>>>> I am rebuilding with debug symbols, as when I tried to view
>>>>>> chrome.core in gdb, it just gave me a huge backtrace of "??"
>>>>>> instances.
>>>>>>
>>>>>> I had Chromium 18 running successfully with an older version of the
>>>>>> ports tree, built from source. But I can't reproduce that.
>>>>>>
>>>>>> I'm building inside a VirtualBox instance, if that makes any difference.
>>>>>>
>>>>>> I recognize this all may not be a very useful bug report, but I'm
>>>>>> still learning to file useful ones, so please bear with me.
>>>>>> _______________________________________________
>>>>>> freebsd-chromium at freebsd.org mailing list
>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-chromium
>>>>>> To unsubscribe, send any mail to "freebsd-chromium-unsubscribe at freebsd.org"
>>>>>
>>>>> Confirmed, I got the same on my eeepc.
>>>>>
>>>>> regards,
>>>>> Bapt
>>>>
>>>> Debug build works for me under i386 vm, release crashes... I didn't
>>>> have enough time to debug this.
>>>>
>>>> Feedback is always welcome and needed.
>>>>
>>>>
>>>> Regards,
>>>> George
>>>
>>> What do you mean by "debug build" -- one with debug symbols enabled
>>> during make configure?
>>>
>>> I tried to build that and the build failed, and I gave up at that
>>> point, but I can keep trying.
>>>
>>> Of course, the reason I was trying to do the debug build was to find
>>> the problem, but are you saying that enabling the debug symbols
>>> somehow fixes the problem?
>>>
>>> -- David.
>>
>> Yes, with the debug option enabled chromium does not crash. It only
>> produces some error messages from the GPU thread about libGL being
>> old.
>>
>> Most probably you are running out of memory, that is why you cannot
>> finish the compile. I had to add swap.. even though my desktop has
>> 16GiB of ram they are not usable from the vm, i will try to recompile
>> the kernel with PAE.

Wild guess, it could be a macro using NDEBUG to abort.