public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
To: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix problems with finishing a dummy function call on simulators.
Date: Tue, 09 Jun 2015 18:22:00 -0000	[thread overview]
Message-ID: <55772ECA.7040105@codesourcery.com> (raw)
In-Reply-To: <55772CD8.9070106@redhat.com>

On 06/09/2015 03:13 PM, Pedro Alves wrote:
> On 06/09/2015 07:10 PM, Luis Machado wrote:
>
>>> Not exactly sure what to do here.  Maybe we should stop considering
>>> permanent and non-permanent breakpoints at the same address as
>>> duplicates.  That should result in GDB inserting the non-permanent
>>> one, I think.  Or we could get stop marking permanent breakpoints
>>> as always inserted, and let normal breakpoints insert on top of
>>> permanent breakpoints normally.  See also:
>>>    https://sourceware.org/ml/gdb-patches/2015-03/msg00174.html
>>
>> That sounds a bit hacky.
>
> Can you clarify?  There are two suggestions above, in addition
> to a url showing even more ideas.  So I don't know what you're
> referring to.  :-)

Both the above and the mail sound like workaround ideas. You mentioned 
even more special casing in the mail. It is the amount of special casing 
that i'm afraid of.

Having more special cases feel like they defeat the purpose of having 
those permanent breakpoints if we have to IF our way through them. Am i 
missing something?

  reply	other threads:[~2015-06-09 18:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 15:01 Luis Machado
2015-06-09 17:51 ` Pedro Alves
2015-06-09 18:10   ` Luis Machado
2015-06-09 18:13     ` Pedro Alves
2015-06-09 18:22       ` Luis Machado [this message]
2015-06-09 18:34       ` Luis Machado
2015-06-16 17:39   ` Luis Machado
2015-06-17 12:41     ` Pedro Alves
2015-06-17 13:26       ` Luis Machado
2015-06-17 13:43         ` Pedro Alves
2015-06-17 20:16           ` Luis Machado
2015-07-06 15:06             ` Pedro Alves
2015-07-06 15:33               ` Luis Machado
2015-07-06 16:15                 ` Pedro Alves
2015-07-06 16:18                   ` Luis Machado
2015-07-06 18:34                   ` Luis Machado
2015-07-06 19:07                     ` Pedro Alves
2015-07-06 19:11                       ` Luis Machado

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=55772ECA.7040105@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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).