From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11239 invoked by alias); 27 Sep 2002 19:02:20 -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 11230 invoked from network); 27 Sep 2002 19:02:18 -0000 Received: from unknown (HELO c007.snv.cp.net) (209.228.33.228) by sources.redhat.com with SMTP; 27 Sep 2002 19:02:18 -0000 Received: (cpmta 18575 invoked from network); 27 Sep 2002 12:02:17 -0700 Received: from 65.85.219.162 (HELO intellibot.cc) by smtp.intellibot.cc (209.228.33.228) with SMTP; 27 Sep 2002 12:02:17 -0700 X-Sent: 27 Sep 2002 19:02:17 GMT Date: Fri, 27 Sep 2002 12:02:00 -0000 Mime-Version: 1.0 (Apple Message framework v546) Content-Type: multipart/alternative; boundary=Apple-Mail-2--988439221 Subject: gdb is breaking at wrong locations From: David Knuth To: gdb@sources.redhat.com Message-Id: X-SW-Source: 2002-09/txt/msg00487.txt.bz2 --Apple-Mail-2--988439221 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Content-length: 1092 Hi, We've got an m68k-coff tool chain to develop for and debug a 68332 board via BDM. I'm using gdb 4.17 and an ICD BDM pod. Today, I noticed that it is not stopping at the set break points. It is stopping about 6 lines after it should, thus it is stopping at times when I don't expect it to. All the break points are at lines the are the else of an if condition and all are a return error; statement. Also, gdb is crashing frequently, or at least it's telling me there's a SIGBUS fault and it cannot proceed. 1) Are there somethings I should look out for when setting break points? Any no-nos? 2) Can I/ should I upgrade to a later version of GDB? Will a newer version work with the older gcc/as/ld/ar tools I'm using now? As a side note, I've noticed that if I remove the parallel port extension cable between the laptop and BDM pod, the number of crashes decreases. The problem with not breaking at the right location does not go away, however. David ======================================================== David Knuth dknuth@intellibot.cc (804) 543-2703 --Apple-Mail-2--988439221 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII Content-length: 1128 Hi, We've got an m68k-coff tool chain to develop for and debug a 68332 board via BDM. I'm using gdb 4.17 and an ICD BDM pod. Today, I noticed that it is not stopping at the set break points. It is stopping about 6 lines after it should, thus it is stopping at times when I don't expect it to. All the break points are at lines the are the else of an if condition and all are a return error; statement. Also, gdb is crashing frequently, or at least it's telling me there's a SIGBUS fault and it cannot proceed. 1) Are there somethings I should look out for when setting break points? Any no-nos? 2) Can I/ should I upgrade to a later version of GDB? Will a newer version work with the older gcc/as/ld/ar tools I'm using now? As a side note, I've noticed that if I remove the parallel port extension cable between the laptop and BDM pod, the number of crashes decreases. The problem with not breaking at the right location does not go away, however. David ======================================================== David Knuth dknuth@intellibot.cc (804) 543-2703 --Apple-Mail-2--988439221--