Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Jason Molenda" <jmolenda@apple.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: deferred breakpoints
Date: Wed, 26 Feb 2003 02:22:00 -0000	[thread overview]
Message-ID: <001e01c2dd3e$619dd640$2a00a8c0@dash> (raw)
In-Reply-To: <38D95BB0-490C-11D7-83B0-003065BC3540@apple.com>

> Our developers use the future-breaks a lot here at Apple, they work
> well for the sort of problem you're looking at.

Thanks for responding Jason.  I'm curious: are these patches in use at Apple
not considered suitable for submission to the FSF?  I'm just wondering why
you maintain a separate tree rather than pushing everything out.  We're
trying hard to get all our changes rolled in to avoid the hassle of having a
separate tree.

cheers,

Kris


  reply	other threads:[~2003-02-26  2:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 21:36 Kris Warkentin
2003-02-25 21:59 ` Jason Molenda
2003-02-26  2:22   ` Kris Warkentin [this message]
2003-02-26  2:26     ` gdb detach Smita
2003-02-26  4:47     ` deferred breakpoints Jason Molenda
2003-02-26 16:51       ` Kris Warkentin
     [not found] <1046355813.623.ezmlm@sources.redhat.com>
2003-03-01  2:16 ` Jim Ingham
  -- strict thread matches above, loose matches on Subject: below --
2003-02-25 20:51 Kris Warkentin
2003-02-25 20:57 ` Daniel Jacobowitz

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='001e01c2dd3e$619dd640$2a00a8c0@dash' \
    --to=kewarken@qnx.com \
    --cc=gdb@sources.redhat.com \
    --cc=jmolenda@apple.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