Bug 102634
| Summary: | res_query reports error in multi threaded application | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Saurabh Mathur <smathur> |
| Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
| Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | 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: | 2003-11-05 18:52:53 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: | |||
i assign it to correct component Please supply a minimal testcase to show what exactly you're doing and what you expect it to do. Ping. Without a test case we cannot do anything. I'll keep the bug open for a bit longer. No response in a month. No bug in sight. Closing. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 Description of problem: We have written a simple application for doing SMTP MX record query using the res_query function. This API returns error "No such process" (error number 3) whenever it is called from a thread that has been invoked. From the main thread or single threaded application, this API works fine. The same sample test applicaiton works fine when compiled and run on 6.2 redhat Linux installation in single and multi threaded application but fails on the Redhat 8.0 release. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Write a multi threaded program. 2. From the new thread, call res_query for MX records. 3. In case, error is returned, print the error string. Actual Results: The program retuns "No Such Process" Expected Results: It must have done the DNS resolution for MX record and returned the IP address of the machine. Additional info: