From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16505 invoked by alias); 30 Nov 2005 04:21:41 -0000 Received: (qmail 16498 invoked by uid 22791); 30 Nov 2005 04:21:40 -0000 X-Spam-Check-By: sourceware.org Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.196) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 30 Nov 2005 04:21:38 +0000 Received: by zproxy.gmail.com with SMTP id x3so171700nzd for ; Tue, 29 Nov 2005 20:21:37 -0800 (PST) Received: by 10.36.227.25 with SMTP id z25mr5330928nzg; Tue, 29 Nov 2005 20:21:37 -0800 (PST) Received: by 10.37.2.35 with HTTP; Tue, 29 Nov 2005 20:21:37 -0800 (PST) Message-ID: <8f2776cb0511292021u681b3ac4od01b67ac01ffc37f@mail.gmail.com> Date: Wed, 30 Nov 2005 04:23:00 -0000 From: Jim Blandy To: yang xiaoli Subject: Re: local gdb could not stop at breakpoint? Cc: gdb@sourceware.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <8f2776cb0511282201y3fcbd125w16da2303780954aa@mail.gmail.com> 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: 2005-11/txt/msg00634.txt.bz2 On 11/29/05, yang xiaoli wrote: > Jim Blandy: > yes, this time I compile gdb-6.3 for native debugger, it can stop at > breakpoints, Maybe gdb-6.0 is too old. Thanks for your help. That's great! > configure script has a problem, I modified gdb-6.3/readline/configure at > line 6261: > erase "{ (exit 1); exit 1; };" > so it can cross-compile to native debugger. We use GNU autoconf to generate the 'configure' script automatically from 'configure.ac', so fixing 'configure' itself won't work. What was the problem you encountered? Did it print an error message? (When you want to show changes to a file, it is a good idea to post a patch, produced by 'diff' or (if you're using the current sources) 'cvs diff'. See the archives of the 'gdb-patches' mailing list for lots of examples of people doing this. In this case, what you posted was clear enough, but for larger changes, a diff is really necessary.)