Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
	       Jan Kratochvil <jan.kratochvil@redhat.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH 2/6] Introduce `pre_expanded sals'
Date: Fri, 05 Aug 2011 03:41:00 -0000	[thread overview]
Message-ID: <m3fwlgcypb.fsf@redhat.com> (raw)
In-Reply-To: <m31ux0zz94.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu,	04 Aug 2011 14:40:39 -0600")

Tom Tromey <tromey@redhat.com> writes:

>>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
> Tom> Yesterday I started wondering if this patch series could go in if
> Tom> re-expressed as catchpoints.
>
> Sergio> IMHO this is OK.  I would prefer to see this command as a breakpoint
> Sergio> because I have always seen catchpoints as "event-oriented breakpoints",
> Sergio> such as the calling/returning of a syscall, or a fork, or exec.
>
> However, I thought of one other reason we might prefer a catchpoint: if
> we add "objfile:"-style linespecs ("break libc.so:malloc"), then we are
> going to run into trouble if anybody tries to debug a program named
> "probe" -- because "break probe:spec" is handled pretty early in
> linespec.

All right, I see what you mean.  Personally, I think that if this
behavior happens, then it means we should probably fix linespec in order
to evaluate the `probe:' part earlier.

Anyway, as I said in my earlier reply, I think that holding the stap
patch because of this change in particular is something we may not want
(I certainly don't), so for me this is the strongest argument for why we
could change it from breakpoint to catchpoint.

> Let me know what you think.  In the absence of comments I am going to
> implement this.

As I said in the beginning, I'm OK with that change.  But obviously I'm
not a maintainer, and I'm also an interested part in this being accepted
:-).


  reply	other threads:[~2011-08-05  3:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  3:08 Sergio Durigan Junior
2011-04-06 20:13 ` Tom Tromey
2011-04-12 11:18   ` Pedro Alves
2011-04-12 11:53     ` Jan Kratochvil
2011-04-12 13:30       ` Pedro Alves
2011-04-12 20:34         ` Tom Tromey
2011-04-12 22:22         ` Matt Rice
2011-04-13  9:53           ` Eli Zaretskii
2011-07-27 17:08         ` Tom Tromey
2011-07-29 20:36           ` Sergio Durigan Junior
2011-08-04 20:41             ` Tom Tromey
2011-08-05  3:41               ` Sergio Durigan Junior [this message]
2011-08-05 14:40                 ` Tom Tromey
2011-08-05 18:06                   ` Sergio Durigan Junior
2011-08-10 14:24           ` Tom Tromey
2011-05-03 16:09       ` Jerome Guitton
2011-05-03 18:17         ` Joel Brobecker
2011-04-12 20:26     ` Tom Tromey
2011-04-13  9:51       ` Eli Zaretskii
2011-04-13 19:20         ` Tom Tromey
2011-04-15 10:37           ` Eli Zaretskii
2011-04-18 18:37       ` Pedro Alves
2011-04-27 18:02         ` Jan Kratochvil
2011-04-29 20:42         ` Tom Tromey
2011-04-11 21:08 ` Jan Kratochvil

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=m3fwlgcypb.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=pedro@codesourcery.com \
    --cc=tromey@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