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 441663 - gdm crashes with SIGSEGV in add_auth_entry()
gdm crashes with SIGSEGV in add_auth_entry()
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
2.19.x
Other Linux
: Normal critical
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-27 20:00 UTC by Sebastien Bacher
Modified: 2007-06-04 04:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Sebastien Bacher 2007-05-27 20:00:26 UTC
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/116392

"Binary package hint: gdm

gdm, as of updating gutsy to the latest, is crashing on me. The stack trace of the crash is:
...
Interesting. Here's the new stacktrace:

(gdb) where
  • #0 add_auth_entry
    at auth.c line 112
  • #1 add_auth_entry_for_addr
    at auth.c line 340
  • #2 get_local_auths
    at auth.c line 474
  • #3 gdm_auth_user_add
    at auth.c line 561
  • #4 gdm_slave_session_start
    at slave.c line 4219
  • #5 gdm_slave_run
    at slave.c line 1591
  • #6 gdm_slave_start
    at slave.c line 892
  • #7 gdm_display_manage
    at display.c line 398
  • #8 gdm_start_first_unborn_local
    at gdm.c line 266
  • #9 main
    at gdm.c line 1832

And here's the problem:

 if (SERVER_IS_LOCAL (d) && ! added_lo && ! d->tcp_disallowed) {
  struct sockaddr_storage *lo_ss = NULL;
  /* FIXME: get loobback ss */
  if (! add_auth_entry_for_addr (d, &auths, lo_ss)) {
   goto get_local_auth_error;
  }
 }

in get_local_auths(). lo_ss == NULL is passed to add_auth_entry_for_addr() which doesn't even test it for NULL and starts using it and ends up assigning one if it's members to "addr" which ends up being used in a memcpy. Bad.
...
I was just about to dig in and get to the root of this problem and saw didier's post. Indeed, disabling TCP solves my crash too. I do like my X server listening on the TCP socket though.
..."
Comment 1 Brian Cameron 2007-06-04 04:42:32 UTC
This has been fixed in SVN head.  See bug #108820.