Bug 77039

Summary: glibc-2.2.93-5 + MySQL-3.23.52-3 = seg fault in _nss_dns_gethostbyaddr_r
Product: [Retired] Red Hat Linux Reporter: tanner
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: fweimer, marcel, natecars
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-11-07 07:45:40 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:

Description tanner 2002-10-31 07:57:14 UTC
Description of Problem:

mysql-3.23.52-3 seg faults on remote network connects. Using the mysql client,
and running mysqld under the debugger. I get this:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 24580 (LWP 6865)]
0x40014098 in _nss_dns_gethostbyaddr_r () from /lib/libnss_dns.so.2
(gdb) bt
#0  0x40014098 in _nss_dns_gethostbyaddr_r () from /lib/libnss_dns.so.2
#1  0x40267cc1 in gethostbyaddr_r@@GLIBC_2.1.2 () from /lib/libc.so.6
#2  0x40267ada in gethostbyaddr () from /lib/libc.so.6
#3  0x080e8476 in ip_to_hostname(in_addr*, unsigned*) (in=0x83d460c,
    errors=0xbf3ff978) at hostname.cc:192
#4  0x080e8faf in check_connections (thd=0x83d4218) at sql_parse.cc:344
#5  0x080e9452 in handle_one_connection(void*) (arg=0xbf3ffd9c)
    at sql_parse.cc:534
#6  0x4003376e in pthread_start_thread () from /lib/libpthread.so.0
#7  0x400337dd in pthread_start_thread_event () from /lib/libpthread.so.0


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

Comment 1 Need Real Name 2002-10-31 22:25:05 UTC
Just wanted to mention that an upgrade to glibc 2.3.1 (built from Rawhide
SRPM's) resolved this problem on our end. So, it is definetly a problem with
MySQL<->glibc interaction (if not a bug in glibc itself).

Comment 2 Marcel Telka 2002-11-07 07:45:34 UTC
This bug is similar to bug 75128.

Comment 3 Jakub Jelinek 2002-12-04 16:51:11 UTC

*** This bug has been marked as a duplicate of 77467 ***