Runtime glibmm exception in me-tv 0.6

Bug #269911 reported by Matthias Adler
4
Affects Status Importance Assigned to Milestone
Me TV
Fix Released
High
Unassigned

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

Revision history for this message
Matthias Adler (matthias-bitshaker) wrote :
Revision history for this message
Matthias Adler (matthias-bitshaker) wrote :
Revision history for this message
Matthias Adler (matthias-bitshaker) wrote :
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Why do you need "--disabled-static --enable-shared"? Can you please try it without those options?

Changed in me-tv:
status: New → Incomplete
Revision history for this message
Matthias Adler (matthias-bitshaker) wrote :

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).

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

0.6.0 has some major issues. Wait for 0.6.1.

Thanks,

Michael

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

0.6.1 released.

Revision history for this message
Jeff Bailes (thepizzaking) wrote :

I'm getting a similar error (not sure if it's the same issue or not), me-tv (0.6.2) builds fine but when I attempt to run it I get the following error:
---
09/24/08 20:25:58: Me TV 0.6.2

glibmm-ERROR **:
unhandled exception (type unknown) in signal handler

aborting...
zsh: abort me-tv
---
If you need any logs or other information just ask.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Hi Jeff,

Which Distro are you using?

Thanks,

Michael

Revision history for this message
Jeff Bailes (thepizzaking) wrote :

I'm running Arch Linux.
glibmm version 2.16.4

Revision history for this message
Matthias Adler (matthias-bitshaker) wrote :

Hi Michael,

I gave 0.6.2 a shot. It compiled just fine, but when attempting to run it, it gave me this output:

09/24/08 15:49:16: Me TV 0.6.2

glibmm-ERROR **:
unhandled exception (type unknown) in signal handler

aborting...

I think Jeff experiences the very same problem. My glibmm version is 2.16.4, too.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

I'm going to need someone to debug this because for some reason the backtrace that was attached shows nothing about Me TV. I can't replicate it. Just use some printf()/g_debug() statements to narrow down the lines of code that are causing it,

Thanks,

Michael

Revision history for this message
Jeff Bailes (thepizzaking) wrote :

I've found (using a backtrace) that the problem is something to do with the channels dialog (not sure exactly what though). If I change line 216 in main_window.cc from:
gint dialog_result = channels_dialog.run();
to:
gint dialog_result = 1; //channels_dialog.run();

me-tv will actually start up, though no channels are listed in the EPG etc (probably because I killed the channels dialog).

I'll attach the backtrace aswell.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Great work Jeff. You can kick off the channels dialog by using View->Channels.

Now, coupled with that backtrace I can see a bit more. Can one of you please replace src/channels_dialog.cc, line 120 onward, with this,

void ChannelsDialog::on_show()
{
 Gtk::Dialog::on_show();
 TRY
 update_channels();
 ChannelList& channels = get_application().get_profile_manager().get_current_profile().get_channels();
 if (channels.size() == 0)
 {
  show_scan_window();
 }
 CATCH
}

Revision history for this message
Matthias Adler (matthias-bitshaker) wrote :

Yay ! I replaced the code and now it works.
Sorry for the bad backtrace, was a bit suprised be this kind of "verbosity".

Anyways, just wanted to let you know that with these changes, there are no more glibmm runtimes errors.

Only other thing I noticed, was that Me-Tv did not recognize my dvb-apps SCAN_DIRECTORY. So I changed line 32 in src/scan_window.h to
#define SCAN_DIRECTORY "/usr/share/dvb-apps"

Is there any way to pass this to the configure script, like "export SCAN_DIRECTORY= "/usr/share/dvb-apps" ?

Changed in me-tv:
assignee: nobody → lamothe
importance: Undecided → High
milestone: none → station-6
status: Incomplete → Fix Committed
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Released in 0.6.3.

Changed in me-tv:
status: Fix Committed → Fix Released
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

To answer your other question, https://answers.edge.launchpad.net/me-tv/+faq/55.

Revision history for this message
Matthias Adler (matthias-bitshaker) wrote :

The runtime glibmm exception has been fixed in 0.6.3. Maybe Jeff can give it try just to be sure. But, I'd say this ticket can be closed. Also, thanks for pointing me to the faq. Next time I'll look there first ;)

Cheers,
Matthias

Revision history for this message
Jeff Bailes (thepizzaking) wrote :

Yeah, I don't get the glibmm error anymore. Though I now get a different error causing me-tv to fail to start up, I'll post it in another bug report though.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.