Bug 110032 - Segment violation on sendmail execution with new glibc upgrade
Summary: Segment violation on sendmail execution with new glibc upgrade
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: glibc
Version: 8.0
Hardware: i586
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-14 08:35 UTC by Javier T
Modified: 2016-11-24 15:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-26 05:15:01 UTC
Embargoed:


Attachments (Terms of Use)
Package list (12.17 KB, text/plain)
2003-11-14 08:45 UTC, Javier T
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.