Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: gdb-patches@sourceware.org, Michael Snyder <msnyder@specifix.com>,
		Daniel Jacobowitz <drow@false.org>
Subject: Re: [RFA] set/show enable-software-singlestep
Date: Wed, 25 Jun 2008 14:42:00 -0000	[thread overview]
Message-ID: <20080625143248.GG3700@adacore.com> (raw)
In-Reply-To: <200806251514.32422.pedro_alves@portugalmail.pt>

> I'm just curious about it,

Sure :).

> I can't figure which targets are used in Tru64.  Is it ptrace based?

Actually, I think it's procfs.

> From your description of not being able to hw singlestep
> threaded programs, I take it threads are user space?

Yes (DEC threads).

> I'm thinking what we want is the other way around.  Can the target
> singlestep itself?  Software-singlestepping with breakpoints is the
> current fallback mechanism.

Ideally, yes. We would like the debugger to automatically detect
whether software single-step is needed or not. The user-setting
is interesting for the cases when this detection is not implemented.
However, I won't argue that the change is so interesting that the
user setting must be checked in now so that we have early access
to it. I'm equally content to NOT have a user setting and let GDB
continue to use s/w single-step by default on Tru64.

> Is there a thread_stratum target used to implement the thread support?

Right now, no. As it turns out, however, it just happens that I
implemented this thread layer for dec-threads a two or three weeks ago.
It's ready to be submitted, but I did the work as quickly as possible
(for internal reasons) and so it seems to work, but I sometimes I have
this uneasy feeling that it's too simplistic.  So I want to give it
a little bit more testing, to see if I can avoid embarrassing myself
with silly code :). Not that it would be the first time, really...

-- 
Joel


  reply	other threads:[~2008-06-25 14:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 18:43 Michael Snyder
2008-06-24 19:15 ` Daniel Jacobowitz
2008-06-24 19:32   ` Michael Snyder
2008-06-25 13:22     ` Joel Brobecker
2008-06-25 13:43       ` Daniel Jacobowitz
2008-06-25 14:15         ` Joel Brobecker
2008-06-25 14:33         ` Pedro Alves
2008-06-25 15:05           ` Daniel Jacobowitz
2008-06-25 15:38             ` Pedro Alves
     [not found]               ` <1214862215.3601.1525.camel@localhost.localdomain>
2008-07-10  2:46                 ` Michael Snyder
2008-07-10 11:07                   ` Pedro Alves
2008-07-10 22:47                     ` Daniel Jacobowitz
2008-07-12  2:31                       ` Michael Snyder
2008-07-12  2:28                     ` Michael Snyder
2008-06-25 14:35       ` Pedro Alves
2008-06-25 14:42         ` Joel Brobecker [this message]
2008-06-24 19:25 ` Eli Zaretskii
2008-06-24 19:34 ` Luis Machado
2008-06-24 20:22   ` Michael Snyder
2008-06-25  1:40 ` Pedro Alves
2008-06-25  6:15   ` Michael Snyder

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=20080625143248.GG3700@adacore.com \
    --to=brobecker@adacore.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@specifix.com \
    --cc=pedro_alves@portugalmail.pt \
    /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