From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6511 invoked by alias); 14 Jun 2005 21:24:44 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6502 invoked by uid 22791); 14 Jun 2005 21:24:41 -0000 Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 14 Jun 2005 21:24:41 +0000 Received: from elgar.sibelius.xs4all.nl (root@elgar.sibelius.xs4all.nl [192.168.0.2]) by sibelius.xs4all.nl (8.13.0/8.13.0) with ESMTP id j5ELOdbf002005 for ; Tue, 14 Jun 2005 23:24:39 +0200 (CEST) Received: from elgar.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by elgar.sibelius.xs4all.nl (8.13.4/8.13.3) with ESMTP id j5ELOd5w024422 for ; Tue, 14 Jun 2005 23:24:39 +0200 (CEST) Received: (from kettenis@localhost) by elgar.sibelius.xs4all.nl (8.13.4/8.13.4/Submit) id j5ELOY8L022852; Tue, 14 Jun 2005 23:24:34 +0200 (CEST) Date: Tue, 14 Jun 2005 21:24:00 -0000 Message-Id: <200506142124.j5ELOY8L022852@elgar.sibelius.xs4all.nl> From: Mark Kettenis To: gdb@sources.redhat.com In-reply-to: <20050614205212.GK62467@keyslapper.net> (message from Louis LeBlanc on Tue, 14 Jun 2005 16:52:12 -0400) Subject: Re: stack corruption? References: <20050614014520.GG24814@keyslapper.net> <20050614020138.GA19453@nevyn.them.org> <20050614033256.GB48802@keyslapper.net> <10DBEAA7-48B2-4298-A8CC-58A138415516@apple.com> <20050614205212.GK62467@keyslapper.net> X-SW-Source: 2005-06/txt/msg00144.txt.bz2 Date: Tue, 14 Jun 2005 16:52:12 -0400 From: Louis LeBlanc BTW, I've seen problems in several applications while performing network lookups, not just my code, and not just C programs. I got a couple created by Perl scripts a couple weeks ago and they were also in the middle of network lookups. This makes me skeptical of the system libs, not my code and not gcc. The real problem is that gdb tells me nothing useful in these cases, unless the corrupt stack message is a real issue with my code. But unless you're going to send us a transcript of your debug session with the *exact* messages, we won't be able to help you. Mark