public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Guillaume Savaton <guillaume.savaton@eseo.fr>
To: insight@sources.redhat.com
Subject: Re: Make breakpoint pending
Date: Thu, 09 Mar 2006 16:39:00 -0000	[thread overview]
Message-ID: <44105A23.7070705@eseo.fr> (raw)
In-Reply-To: <44105338.20004@redhat.com>

Keith Seitz wrote :
>> This message is quite annoying since I am asked to confirm for each 
>> breakpoint in my program individually.
> 
> If you look at the breakpoints which 
> were marked pending, are they part of your program?

Well, for instance, I have a "start" label at the beginning of my program.
Usually, in the "target settings" dialog, I tell insight to place a breakpoint
at label "start".

It is the only breakpoint set in my program, and it actually belongs to the program.
But before running, the "make breakpoint pending..." message pops up.

N.B: I am using insight compiled for arm-elf targets.
All my programs are written in assembly language.
The executable is generated using GNU as and ld.
The same behavior has been noticed whether the debug target is set to
"Simulator" or "Remote TCP"

 >> Is there a possibility to tell insight not to ask ?
 >
 > Yes, you can add it to the ignored warnings list or teach insight that
 > it is an ignorable warning (so it will only ask once). See
 > gdbtk_tcl_warning in interface.tcl to globally ignore the warning.

I will try this.

Thanks for your help.

Guillaume Savaton

  reply	other threads:[~2006-03-09 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22  4:14 Need Help Amarnath
2006-03-02  8:51 ` Make breakpoint pending Guillaume Savaton
2006-03-09 16:09   ` Keith Seitz
2006-03-09 16:39     ` Guillaume Savaton [this message]
2006-03-09 16:45       ` Keith Seitz
2006-03-09 17:08         ` Guillaume Savaton
2006-03-09 17:12           ` Keith Seitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44105A23.7070705@eseo.fr \
    --to=guillaume.savaton@eseo.fr \
    --cc=insight@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).