From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8767 invoked by alias); 27 Sep 2006 19:58:28 -0000 Received: (qmail 8753 invoked by uid 22791); 27 Sep 2006 19:58:26 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 27 Sep 2006 19:58:22 +0000 Received: (qmail 12587 invoked from network); 27 Sep 2006 19:58:20 -0000 Received: from unknown (HELO localhost) (jimb@127.0.0.2) by mail.codesourcery.com with ESMTPA; 27 Sep 2006 19:58:20 -0000 To: "Mitchell Fang" Cc: gdb@sourceware.org Subject: Re: GDB stub - connection from 32 bit GDB or 64 bit GDB References: From: Jim Blandy Date: Wed, 27 Sep 2006 19:58:00 -0000 In-Reply-To: (Mitchell Fang's message of "Wed, 27 Sep 2006 10:34:45 -0700") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00171.txt.bz2 "Mitchell Fang" writes: > How can the gdb stub know if a 32 bit GDB is connecting to the stub > or a 64 bit GDB is connecting to the stub? Is it even possible? It > doesn't seem possible to me looking at the current gdb remote > commands, but hopefully I overlooked something. > I have tried different combinations with 32-bit and 64-bit GDBs and > gdbservers and it seems like a 32 bit GDB will not work with a 64 bit > gdbserver and vice versa. You haven't provided enough information for us to help you. I assume you're having some troubles connecting a particular GDB with a particular stub, but when you wrote your message, you guessed that the problem was a 32-bit vs. 64-bit problem, and then wrote your message to provide only enough information for us to help you *if* your guess was right. Instead, simply describe to us the problem you're having, without guessing about the underlying cause: - What is the program you're trying to debug running on? What processor architecture? Is it an evaluation board? - What kind of machine is GDB running on? What operating system is it running? - How is GDB connecting to the program you're trying to debug? The remote protocol? gdbserver? RedBoot? A custom stub built into the eval board? - What happened when you tried to connect? What was the exact error message? Can you cut and paste the session from your terminal?