[Gaim-bugs] [ gaim-Bugs-1696667 ] Seg Fault on startup

2007-04-09 Thread SourceForge.net
Bugs item #1696667, was opened at 2007-04-08 20:53
Message generated for change (Comment added) made by lschiere
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100235&aid=1696667&group_id=235

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: segfault
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: ynnad (ynnad)
>Assigned to: Nathan Walp (faceprint)
Summary: Seg Fault on startup

Initial Comment:
Gaim suddenly started seg faulting on startup.
The only thing I think of is that I was playing around with PostgreSQL.

--

>Comment By: Luke Schierer (lschiere)
Date: 2007-04-09 15:20

Message:
Logged In: YES 
user_id=28833
Originator: NO

GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db
library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) r
Starting program: /usr/local/bin/gaim 
[Thread debugging using libthread_db enabled]
[New Thread -1220630336 (LWP 9700)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1220630336 (LWP 9700)]
0xb7129279 in jabber_send_raw (js=0x0, data=0xb7134f30 "",
len=-1) at jabber.c:253
253 gaim_debug(GAIM_DEBUG_MISC, "jabber", "Sending%s: %s\n",
(gdb) bt full
#0  0xb7129279 in jabber_send_raw (js=0x0, data=0xb7134f30
"", len=-1) at jabber.c:253
ret = 
#1  0xb7129492 in jabber_close (gc=0x8395040) at jabber.c:937
js = (JabberStream *) 0x0
#2  0xb77e3c03 in gaim_connection_destroy (gc=0x8395040) at
connection.c:196
account = (GaimAccount *) 0x81271e0
buddies = 
tmp = 
__PRETTY_FUNCTION__ = "gaim_connection_destroy"
#3  0xb77d4633 in gaim_account_disconnect (account=0x81271e0) at
account.c:1019
gc = (GaimConnection *) 0xb7134f0e
__PRETTY_FUNCTION__ = "gaim_account_disconnect"
#4  0xb780296d in gaim_prpl_change_account_status (account=0x81271e0,
old_status=0x8124340, new_status=0x8124910) at prpl.c:177
__PRETTY_FUNCTION__ = "gaim_prpl_change_account_status"
#5  0xb780f75d in gaim_status_set_active_with_attrs_list
(status=0x8124910, active=1, attrs=0x0) at status.c:657
account = (GaimAccount *) 0x81271e0
ops = (GaimAccountUiOps *) 0x80e592c
changed = 1
l = 
specified_attr_ids = (GList *) 0x0
status_type = 
__PRETTY_FUNCTION__ = "gaim_status_set_active_with_attrs_list"
#6  0xb77d3b2a in gaim_account_set_status_list (account=0x81271e0,
status_id=0x8123878 "offline", active=1, attrs=0x0) at account.c:1410
status = (GaimStatus *) 0x8124910
__PRETTY_FUNCTION__ = "gaim_account_set_status_list"
#7  0xb77d3c33 in gaim_account_set_status (account=0x81271e0,
status_id=0x8123878 "offline", active=1) at account.c:1385
attrs = 
id = 
args = 0xbf8f74b0
"[EMAIL 
PROTECTED]"\203·Àþ1\bàq\022\bøt\217¿€\201\200·š­\022\bàq\022\b\t\210\202·"
#8  0xb7807bc7 in gaim_savedstatus_activate_for_account
(saved_status=0x812ada8, account=0x81271e0) at savedstatuses.c:1124
status_type = (const GaimStatusType *) 0x8123850
message = 0x0
__PRETTY_FUNCTION__ = "gaim_savedstatus_activate_for_account"
#9  0xb78081a4 in gaim_savedstatus_set_idleaway (idleaway=0) at
savedstatuses.c:852
account = (GaimAccount *) 0x81271e0
presence = 
status = 
accounts = (GList *) 0x831fec0
node = (GList *) 0x831fec0
old = (GaimSavedStatus *) 0x812ac10
saved_status = (GaimSavedStatus *) 0x812ada8
#10 0xb77ef61a in check_idleness () at idle.c:163
time_idle = 0
auto_away = 
idle_reporting = (const gchar *) 0x810c8e8 "system"
l = 
#11 0xb7809e98 in gaim_marshal_VOID__POINTER (cb=0xb77ef660
, args=0xbf8f75c8 "@P9\b0\203\a", data=0x0, return_val=0x0)
at signals.c:628
No locals.
#12 0xb780a7e9 in gaim_signal_emit_vargs (instance=0xb783347c,
signal=0xb78267aa "signing-on", args=0xbf8f75c8 "@P9\b0\203\a") at
signals.c:481
handler_data = (GaimSignalHandlerData *) 0x0
l = 
l_next = (GList *) 0x0
tmp = 0xbf8f75c8 "@P9\b0\203\a"
__PRETTY_FUNCTION__ = "gaim_signal_emit_vargs"
#13 0xb780a8fc in gaim_signal_emit (instance=0x8127c0c, signal=0x0) at
signals.c:433
args = 0xbf8f75c8 "@P9\b0\203\a"
__PRETTY_FUNCTION__ = "gaim_signal_emit"
#14 0xb77e3e33 in gaim_connection_new (account=0x81271e0, regist=0,
password=0x81238d8 "quartz91") at connection.c:140
gc = (GaimConn

[Gaim-bugs] [ gaim-Bugs-1696667 ] Seg Fault on startup

2007-04-08 Thread SourceForge.net
Bugs item #1696667, was opened at 2007-04-09 10:53
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100235&aid=1696667&group_id=235

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: segfault
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: ynnad (ynnad)
Assigned to: Nobody/Anonymous (nobody)
Summary: Seg Fault on startup

Initial Comment:
Gaim suddenly started seg faulting on startup.
The only thing I think of is that I was playing around with PostgreSQL.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100235&aid=1696667&group_id=235

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Gaim-bugs mailing list
Gaim-bugs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gaim-bugs