Bug 318937 – Pointer truncated on Alpha

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 318937 - Pointer truncated on Alpha


Summary:	Pointer truncated on Alpha


Status:	RESOLVED OBSOLETE

Product:	gossip
Classification:	Deprecated
Component:	General
Version:	0.8.0
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Gossip Maintainers
QA Contact:	Gossip Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-10-15 14:11 UTC by Ross Burton
Modified:	2006-04-09 16:14 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Ross Burton 2005-10-15 14:11:13 UTC

[forwarded from http://bugs.debian.org/294279]

0x0000000120048dbc in startup_druid_get_account_info (
    startup_druid=0x12017d570, account=0x11fce3508)
    at gossip-startup-druid.c:211
211                             server = server_entry->address;
(gdb) bt

+ Trace 63550

#0 startup_druid_get_account_info
at gossip-startup-druid.c line 211
#1 startup_druid_prepare_page_last
at gossip-startup-druid.c line 246
#2 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#3 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#4 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#5 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#6 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#7 gnome_druid_page_prepare
from /usr/lib/libgnomeui-2.so.0
#8 gnome_druid_set_page
from /usr/lib/libgnomeui-2.so.0
#9 gnome_druid_get_type
from /usr/lib/libgnomeui-2.so.0
#10 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#16 _gtk_button_set_depressed
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#18 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#24 _gtk_button_paint
from /usr/lib/libgtk-x11-2.0.so.0
#25 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#26 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#27 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#31 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#34 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#35 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#36 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#37 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#38 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#39 gossip_startup_druid_run
at gossip-startup-druid.c line 429
#40 gossip_app_init
at gossip-app.c line 426
#41 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#42 g_object_thaw_notify
from /usr/lib/libgobject-2.0.so.0
#43 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#44 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#45 g_object_new
from /usr/lib/libgobject-2.0.so.0
#46 gossip_app_create
at gossip-app.c line 1121
#47 main
at gossip-main.c line 166

server_entry = (ServerEntry *) 0x2009a130
username = (const gchar *) 0x1201c4d10 "mellum"
server = (const gchar *) 0x12007929a ""
toggle = (GtkToggleButton *) 0x120270dc0
has_account = 0
predefined_server = 1
option_menu = (GtkOptionMenu *) 0x12022c270
(gdb) print *server_entry 
Cannot access memory at address 0x2009a130
(gdb) print *((ServerEntry *) 0x12009a130)
$2 = {label = 0x12007926e "Jabber.org", address = 0x120079279 "jabber.org"}

Clearly, server_entry has been cropped to 32 bit somewhere.

Comment 1 Richard Hult 2006-02-25 16:36:38 UTC

Could you try this with 0.10? The startup code has been rewritten so that file doesn't exist anymore.

Comment 2 Martyn Russell 2006-03-17 00:37:14 UTC

Almost a month has past with no reply here... I am marking this as OBSOLETE unless the bug reporter wants to reopen it.

Comment 3 Ross Burton 2006-03-17 09:19:25 UTC

I'm slacking.  The reporter says it doesn't crash any more but doesn't connect.  Debug log:


falk@juist:~% LM_DEBUG=NET gossip
Going to connect to jabber.org
Trying 208.245.212.98 port 5222...

SEND:
-----------------------------------
<?xml version='1.0' encoding='UTF-8'?>
-----------------------------------

SEND:
-----------------------------------
<stream:stream xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" to="jabber.org" id="msg_1">
-----------------------------------

RECV [153]:
-----------------------------------
'<?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='588519973' from='jabber.org' xml:lang='en'>'
-----------------------------------

SEND:
-----------------------------------
<iq type="set" to="jabber.org" id="msg_2">  <query xmlns="jabber:iq:register">  <username>testasdf123@jabber.org/foo</username>
  <password>foobar</password>
</query>
</iq>

-----------------------------------

RECV [271]:
-----------------------------------
'<iq from='jabber.org' id='msg_2' type='error'><query xmlns='jabber:iq:register'>  <username>testasdf123@jabber.org/foo</username>
  <password>foobar</password>
</query><error code='400' type='modify'><bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>'
-----------------------------------

I'm tempted to say "wrong password" but I don't understand the jabber protocol well enough to say that for sure.

Comment 4 Richard Hult 2006-03-18 11:17:52 UTC

Why are you reusing the bug for something completely different? :)

Comment 5 Martyn Russell 2006-04-09 16:14:51 UTC

I agree with Richard, can you open a new bug for this - if it still exists :)