public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: "Edward L. Hepler" <hepler@vlsi-concepts.com>
Cc: insight@sources.redhat.com
Subject: Re: Adding a target?
Date: Sun, 09 Mar 2008 23:49:00 -0000	[thread overview]
Message-ID: <47D47781.8090104@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.62.0803091319440.443@manx.misty.com>

Edward L. Hepler wrote:

> It appears that the "to_insert_breakpoint" function is not getting called.

Wow... This could require more specialized help...

> Do you know of changes that might have caused this to break?
> Is there some reason why the "to_insert_breakpoint" structure item
> would not be overloaded with the vr2000 entry when the ops target
> is changed?

I neither see anything obvious nor do I recall any changes in this area. 
If your target vector's to_insert_breakpoint method is not being called, 
your best bets are to chase down why to_insert_breakpoint is being set 
to ignored (perhaps some new target vector ops have been inserted since 
the release and you need to update your target vector definition?) or 
you should contact gdb@sourceware.org and ask those people, since they 
are in a much better position to help figure this one out. [I presume 
that just using the command line exhibits the same problem...]

I wish I could be more help, but I've been too idle in gdb internals to 
be able to help you efficiently.

Keith

PS. I will commit a patch for the default portname thing you pointed out.

      reply	other threads:[~2008-03-09 23:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26  3:07 Edward L. Hepler
2008-02-26 18:13 ` Dave Korn
2008-03-06  3:31   ` Edward L. Hepler
2008-02-29  5:38 ` Keith Seitz
     [not found]   ` <Pine.GSO.4.62.0803081507200.8750@manx.misty.com>
2008-03-09 17:34     ` Edward L. Hepler
2008-03-09 23:49       ` Keith Seitz [this message]

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=47D47781.8090104@redhat.com \
    --to=keiths@redhat.com \
    --cc=hepler@vlsi-concepts.com \
    --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).