Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Jan 2015 03:22:05 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 196959] audio/libmusicbrainz5: Use of undefined std:string behaviour causes sound-juicer crash
Message-ID:  <bug-196959-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196959

            Bug ID: 196959
           Summary: audio/libmusicbrainz5: Use of undefined std:string
                    behaviour causes sound-juicer crash
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: jhale@FreeBSD.org
          Reporter: peter@peterjohanson.com
             Flags: maintainer-feedback?(jhale@FreeBSD.org)
          Assignee: jhale@FreeBSD.org

In diagnosing an issue w/ Sound Juicer (audio/sound-juicer) crashing on startup
on FreeBSD-11.0-CURRENT (https://bugzilla.gnome.org/show_bug.cgi?id=742019),
research ultimately showed that the crash was thanks to libmusicbrainz5
depending on undefined behaviour of the std::string constructor which happens
to work on Linux. (it is passing NULL to the std::string constructor, instead
of "")

I have opened a GitHub PR w/ the libmusicbrainz5 project:
https://github.com/metabrainz/libmusicbrainz/pull/6

But so far have gotten no response. With the change in that pull request, Sound
Juicer starts and runs as expected on my system.

I'm a relative newbie to FreeBSD, is the above change something that would
normally get included in the FreeBSD port until upstream fixes and puts out a
new release?

Thanks in advance.

--- Comment #1 from Bugzilla Automation <bugzilla@FreeBSD.org> ---
Auto-assigned to maintainer jhale@FreeBSD.org

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196959-13>