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 360907 - gdm segfaults on ia64 with in ve_locale_from_utf8: address out of bounds
gdm segfaults on ia64 with in ve_locale_from_utf8: address out of bounds
Status: RESOLVED INCOMPLETE
Product: gdm
Classification: Core
Component: general
2.14.x
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-09 14:01 UTC by Sebastien Bacher
Modified: 2007-02-09 17:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Sebastien Bacher 2006-10-09 14:01:27 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/gdm/+bug/62356

"Binary package hint: gdm

I'll attach a backtrace
...
http://librarian.launchpad.net/4440729/gdb-gdmgreeter.txt
backtrace
...
Program received signal SIGSEGV, Segmentation fault.
0x2000000000fc63f0 in g_utf8_validate () from /usr/lib/libglib-2.0.so.0
(gdb) backtrace
  • #0 g_utf8_validate
    from /usr/lib/libglib-2.0.so.0
  • #1 g_convert_with_fallback
    from /usr/lib/libglib-2.0.so.0
  • #2 g_locale_from_utf8
    from /usr/lib/libglib-2.0.so.0
  • #3 ve_locale_from_utf8
    at ve-misc.c line 270
  • #4 greeter_ctrl_handler
    at greeter.c line 259
  • #5 g_io_unix_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0

Comment 1 Brian Cameron 2006-10-10 15:51:28 UTC
Could you let me know what string is being passed into g_locale_from_utf8 as
argument 1?  Perhaps there is something weird about that string?  You may need
to rebuild with -g and attach a debugger to the process that is crashing.

I'm a bit suspicious that this is failing in g_locale_from_utf8.  This may be 
more likely a problem with glib and not GDM unless we are passing some weird
data into the function.  If we are passing in weird data, it would be useful if
you could help identify where the string is coming from.

Also, perhaps Ray Strode could help look into this.   I notice it is failing in 
the g_io code that he recently changed.  I'll cc: him.
Comment 2 Sebastien Bacher 2007-02-09 17:47:13 UTC
comment from the submitter:

"We've gotten rid of of these Itanium1 machines, so I can't try anything
out with them. They were more trouble than they were worth."

Closing the bug for now, I'll reopen if he can the required informations about that