Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: gdb@sourceware.org
Subject: Re: GDB Focus Group at the 2008 GCC Summit
Date: Mon, 23 Jun 2008 22:09:00 -0000	[thread overview]
Message-ID: <200806232208.m5NM8HTZ011692@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20080619190942.GA3744@adacore.com> (message from Joel Brobecker 	on Thu, 19 Jun 2008 15:09:42 -0400)

> Date: Thu, 19 Jun 2008 15:09:42 -0400
> From: Joel Brobecker <brobecker@adacore.com>
> 
> Hello,
> 
> we had a couple of 45min sessions where we discussed various items
> related to GDB. I took some brief notes, although I might have forgotten
> one or two. Anyway, here is what I wrote:
> 
> | * Transition to SVN:
> | 
> |     Required version (for the client) just released a couple of hours ago:
> |     feature allows to checkout a subset of the module (?). There is still
> |     no one-line command that allows to check gdb out, so maybe will have
> |     a script.
> | 
> |     Pb: If we want to have a combined tree, we will need to convert
> |     binutils, gnulib, etc.

Objection!  I have played with SVN for work and I really dilike the
fact that a checked out repository is very grep unfriendly.

> | * Using threads inside GDB:
> | 
> |     Problem: Expression evaluation is synchronous and blocking.
> |     While GDB is doing that work, it is not handling other events,
> |     which can be a problem in non-stop mode.
> |
> |     Typical problem is inferior function call that causes two issues:
> |       - potential length of time it takes to evaluate
> |       - having to re-enter the event loop to wait for function to return.
> | 
> |     Pedro to think about it and write a proposal. Idea we're gearing
> |     towards is one thread that runs the event loop all the time.

I guess something like this is inevitable, but I'm not happy with
using threads.  Threads and signals don't mix really well, and
ptrace(2) depends heavily on threads.


  parent reply	other threads:[~2008-06-23 22:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 19:10 Joel Brobecker
2008-06-22  6:08 ` Thiago Jung Bauermann
2008-06-22 11:52 ` Nick Roberts
2008-06-22 13:53   ` Joel Brobecker
2008-06-23 15:17   ` Tom Tromey
2008-06-23 17:35     ` Jim Ingham
2008-06-23 21:55     ` Nick Roberts
2008-06-23 15:16 ` Tom Tromey
2008-06-26  0:24   ` Tom Tromey
2008-07-03  3:27   ` Thiago Jung Bauermann
2008-07-03  8:12     ` Andreas Schwab
2008-07-03 12:35     ` Daniel Jacobowitz
2008-07-03 14:28       ` Thiago Jung Bauermann
2008-07-04  2:33       ` Tom Tromey
2008-07-04  3:19         ` Daniel Jacobowitz
2008-06-23 21:46 ` Jason Molenda
2008-06-23 22:22   ` Nick Roberts
2008-06-24 21:18     ` Nick Roberts
2008-06-25  6:56       ` [MI] changing breakpoint location (Was: GDB Focus Group at the 2008 GCC Summit) Vladimir Prus
2008-06-23 22:09 ` Mark Kettenis [this message]
2008-06-23 22:26   ` GDB Focus Group at the 2008 GCC Summit Joel Brobecker
2008-06-24  8:35   ` Andrew STUBBS
2008-06-24  8:56     ` Andreas Schwab
2008-06-24 18:12     ` Michael Snyder
2008-06-24 18:28     ` Daniel Jacobowitz
2008-06-24 19:33     ` Dave Korn

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=200806232208.m5NM8HTZ011692@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    /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