X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 83EBF395B044 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1611256138; bh=bEEIQqhNNWwi8+fCzUycFy56GyrZls4f5xE0+GE9ygg=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=sENDl9T42aUv/4VJvOxuHA0kTnR6BEPAkAtMDuwLrbnxkQ1v6xBmmtODPSrgAKhCf P/nRlNKwlBVMUz9gmoH71P5TcqGgN8GjZZyZQsXgAqV5pmyYK3yFSXtdT/F1J65ltw etkxnzP0E0rhfZ72zIy741ZAZ8l9L52cQFVo7Yv0= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org EF71B3959E60 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=nZFcz0jUkKlzWi6NLKSigPxCd1HNEJNcHNxQ0mnyCD8=; b=i3kYv32i1U8IL6KQf5P6pcWNg8MHgwFAJEKLktgFXkQtGGuRaRemjB0F+n5P4eFKSJ h8l20sO5XPmECOrVzpkCgkl377L1V1N3i6VRbELtelg8RDFfFQHXy8NqJvcuGRouG5s/ GUe2VVxzSojawiXMpL/uWeoPNzuV8WydC3ieFq9rE3RfhvzyUmkP3RNu7KGXqvdC40x9 faJB8cZIrOZXEwHOE1HzJrjA58uzMjqoD46BGvaWsRJ6DO2EKFUS6Va89E8ThtkYz5cQ le72WCNS2ODnEFn1Kh99g6ezByMDGFR4fHvzRrVUdq4rg5Ohm83XcMUhwNefRT2XDEma xeTw== X-Gm-Message-State: AOAM532Y3t74VylQE723AMCyUABpUItWv2B0/mjDPIJqP8eWyzMZLaCK 8HpeLqIOXc1OaMy3thXm0Cewbqdvp1Ht1w== X-Google-Smtp-Source: ABdhPJzsOm7TzUey9pCOogURzH7frPjVrTSY7a/htvBRr8EhYMXwkf9vukHhMDo6o6PISC8h+FD0jA== X-Received: by 2002:a1c:3b44:: with SMTP id i65mr715510wma.53.1611256135112; Thu, 21 Jan 2021 11:08:55 -0800 (PST) Subject: Re: gdb not working properly in Cygwin To: cygwin AT cygwin DOT com References: Message-ID: <6c2c9970-9721-af5b-eba0-15555cbb9036@gmail.com> Date: Thu, 21 Jan 2021 20:08:53 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Language: it X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Marco Atzeri via Cygwin Reply-To: Marco Atzeri Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" On 21.01.2021 20:02, Daniel, Barry K. via Cygwin wrote: > I am trying to build and debug a linux application on a Windows 10 machine. I have installed Cygwin64 with GDB and the GCC compliers. When I open up a Cygwin64 terminal and type "gcc -version" or "g++ --version" I get the normal information about those packages. However, when I type in "gdb -version" it print a blank line and I am back at the shell prompt. No text is printed. If I type in "gdb" or "gdb hello.exe", I never get a "(gdb)" prompt. The cursor just sits there and there is no response. I have waited for many minutes with no response. I have to 'Ctrl-Z' to get back the shell prompt. Surely there is a simple solution to this problem but I can't find it anywhere. > > try strace -o /tmp/gdb.strace /usr/bin/gdb --version if there is DLL loading issue should produce a error message -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple