From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1197 invoked by alias); 11 Jan 2002 01:30:18 -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 1016 invoked by uid 22784); 11 Jan 2002 01:30:12 -0000 From: Michael Snyder Newsgroups: cygnus.gdb Subject: Re: 64 bit applications and gdb Date: Thu, 10 Jan 2002 17:30:00 -0000 Organization: Red Hat, Inc. Message-ID: <3C3E3DC5.8ACF6C34@redhat.com> References: <3C3DEFBC.75513D1@get2chip.com> NNTP-Posting-Host: reddwarf.sfbay.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: cronkite.cygnus.com 1010712315 22914 205.180.231.12 (11 Jan 2002 01:25:15 GMT) X-Complaints-To: postmaster@cygnus.com NNTP-Posting-Date: 11 Jan 2002 01:25:15 GMT X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2smp i686) X-Accept-Language: en To: gdb@sources.redhat.com DJ-Gateway: from newsgroup cygnus.gdb X-SW-Source: 2002-01/txt/msg00117.txt.bz2 ccroswhite@get2chip.com wrote: > > GDB folk, > > Having troubles with gdb (4.xx,5.1) analyzing a 64 bit application. I > can not set a break point nothing, after loading the symbol tables I run > the executable and i get this failure: > > (gdb) run > Starting program: /home/csun/meta-g > procfs:4328 -- process not stopped. > procfs: ...giving up... > (gdb) > > Lokks to be an issue with gdb, however, I am not positive. If anyone > could give me some pointers, I would greatly appreciate it. Was your gdb built as a 64-bit solaris application? It needs to be. Turns out that the 64-bit extensions to the /proc interface will not allow a 64-bit process to be debugged by a 32-bit process.