Bug 110032

Summary: Segment violation on sendmail execution with new glibc upgrade
Product: [Retired] Red Hat Linux Reporter: Javier T <ida>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED WORKSFORME QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: drepper, fweimer
Target Milestone: ---   
Target Release: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-26 05:15:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Package list none

Description Javier T 2003-11-14 08:35:08 UTC
Description of problem:

After last update throught rhn from glibc-2.3.2-4.80.6 to glibc-2.3.2-
4.80.8, sendmail cannot start (sendmail-8.12.8-9.80). On command:

sendmail -bd -q1

I obtains this (Spanish):

violacion de segmento.

English: segment violation.

On downgrade all works fine.

Version-Release number of selected component (if applicable):

glibc-2.3.2-4.80.8
glibc-utils-2.3.2-4.80.8
glibc-common-2.3.2-4.80.8
glibc-devel-2.3.2-4.80.8
sendmail-8.12.8-9.80

How reproducible:

Installing new glibc upgrade packages from rhn.

Steps to Reproduce:
1.Upgrade glibc from rhn. glibc-2.3.2-4.80.6 to glibc-2.3.2-4.80.8.
2.Restart sendmail (sendmail-8.12.8-9.80)
  
Actual results:


Expected results:


Additional info:

On other two systems with RH8.0 this update provide no errors on 
sendmail.

Comment 1 Javier T 2003-11-14 08:45:08 UTC
Created attachment 95964 [details]
Package list

Comment 2 Ulrich Drepper 2003-11-14 20:47:46 UTC
The fact that the same code works in your other environments shows
it's something specific for this system, maybe even caused by that
system.  What did sendmail load?  Any milters?  Look at the
/proc/*/maps entry.  Run sendmail within a debugger or at least let it
create a core file and look at it.

Comment 3 Ulrich Drepper 2003-11-20 18:00:01 UTC
Ping.  Do you still see the problem?  Can you run the debugger?  If it
crashes in memory handling, can you run the program under valgrind? 
If we don't get any feedback I assume this is no real problem.

Comment 4 Ulrich Drepper 2004-08-26 05:15:01 UTC
No reply in 9 months, closing.