me-tv-development team mailing list archive
-
me-tv-development team
-
Mailing list archive
-
Message #00394
[Bug 269911] Re: Runtime glibmm exception in me-tv 0.6
I recompiled 0.6 without options "--disable-static --enable-shared" and
the result remains the same. I used above options earlier on, because of
Fedoras packaging guidelines, which do not encourage linking against
static libraries.
Now, the configure script gives me the following output (truncated):
<quote>
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
</quote>
What happens is, me-tv starts up, sometimes even showing the channel-
editor widget, but remaining unresponsive all the time, so it has to be
killed manually (see screenshot).
** Attachment added: "me-tv 0.6 and gdb window side by side"
http://launchpadlibrarian.net/17663906/screenshot2.png
--
Runtime glibmm exception in me-tv 0.6
https://bugs.launchpad.net/bugs/269911
You received this bug notification because you are a member of Me TV
Development, which is subscribed to Me TV.
Status in Me TV, it's TV for me computer: Incomplete
Bug description:
Hi,
I configured me-tv-0.6 with --disabled-static --enable-shared --prefix=/tmp/rpm/me-tv in order to see if everything would build fine.
During make there were mostly no problems, except a few 'is depreciated warning's @see attached metv-0.6-compile-warning.txt.
But when launching me-tv (from BUILDDIR/src/me-tv, that is) it crashed with the following message:
<quote>
glibmm-ERROR **:
unhandled exception (type unknown) in signal handler
aborting...
Cannot access memory at address 0x150a8404
Killed
</quote>
I also attached the suprisingly slim backtrace and infos about installed glibmm packages, as well as the output of /proc/cpuinfo to help you understand where the problem could be.
Cheers,
Matthias
P.S. By the way, xine-lib currently in use is version 1.1.15
References