Bug 43070 - Double-sets a GError somewhere inside the connection code.
Summary: Double-sets a GError somewhere inside the connection code.
Status: RESOLVED NOTOURBUG
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-18 08:47 UTC by Will Thompson
Modified: 2011-11-23 03:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Will Thompson 2011-11-18 08:47:50 UTC 
While I was on a train with terrible 3G yesterday, I saw this in my Gabble debug log:

(telepathy-gabble:22402): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Temporarily unable to resolve '_xmpp-client._tcp.collabora.co.uk'
[Thread 0x7ffff1892700 (LWP 22477) exited]

Unfortunately, I wasn't running with fatal warnings so couldn't get a backtrace. It doesn't seem to be in the code in wocky-connector.c which falls back to connecting directly to the server if the SRV lookup fails.
Comment 1 Jonny Lamb 2011-11-23 03:43:07 UTC 
I've hit this before and for some reason had gdb running (the luck of it!)

It's inside GIO, so not a gabble bug, but I lost the backtrace unfortunately (pastebin expiration times suck) so I can't even push it upstream.

I'll close this bug for now though, OK?

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.