Re: libpam segfault when passwd passes NULL pamh (was Re: gcc -O2 produces invalid object code (x86_64, netbsd-5 branch))

To: NetBSD Toolchain and Build Technical Discussion List <tech-toolchain%NetBSD.org@localhost>
Subject: Re: libpam segfault when passwd passes NULL pamh (was Re: gcc -O2 produces invalid object code (x86_64, netbsd-5 branch))
From: Richard Hansen <rhansen%bbn.com@localhost>
Date: Mon, 08 Mar 2010 15:20:27 -0500

Iain Hibbert wrote:

The pam_check() obfusticates things for no good reason.


Agreed.  I almost nuked the 'end:' label because I thought it was cruft.

-Richard

References:
- gcc -O2 produces invalid object code (x86_64, netbsd-5 branch)
  - From: Richard Hansen
- Re: gcc -O2 produces invalid object code (x86_64, netbsd-5 branch)
  - From: David Holland
- Re: gcc -O2 produces invalid object code (x86_64, netbsd-5 branch)
  - From: Richard Hansen
- Re: gcc -O2 produces invalid object code (x86_64, netbsd-5 branch)
  - From: Joerg Sonnenberger
- libpam segfault when passwd passes NULL pamh (was Re: gcc -O2 produces invalid object code (x86_64, netbsd-5 branch))
  - From: Richard Hansen
- Re: libpam segfault when passwd passes NULL pamh (was Re: gcc -O2 produces invalid object code (x86_64, netbsd-5 branch))
  - From: Joerg Sonnenberger
- Re: libpam segfault when passwd passes NULL pamh (was Re: gcc -O2 produces invalid object code (x86_64, netbsd-5 branch))
  - From: Richard Hansen
- Re: libpam segfault when passwd passes NULL pamh (was Re: gcc -O2 produces invalid object code (x86_64, netbsd-5 branch))
  - From: Iain Hibbert

Home | Main Index | Thread Index | Old Index