Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Cenedese@indel.ch, gdb@sources.redhat.com
Subject: Re: MI: "^running" issues
Date: Thu, 06 Sep 2007 11:39:00 -0000	[thread overview]
Message-ID: <18143.53182.131267.53024@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200709060812.l868ChcE001895@brahms.sibelius.xs4all.nl>

 > > There may be other cases I can't remember now. But I'd surely
 > > welcome a multithreaded gdb. gdb is needed for many cases, not
 > > just a local program on a linux box.
 > 
 > Nothing that you can't solve with non-blocking IO.
 > 
 > Debugging multi-threaded code is bad enough in itself.  You don't need
 > to make matters worse by making gdb itself less deterministic.

Perhaps Fabian is assuming that asynchronus operation requires a multithreaded
gdb.  The async branch that I created was multi-threaded but the patch that I
currently have (under Daniel's guidance) and which I've previously posted to
the gdb-patches mailing list:

http://sourceware.org/ml/gdb-patches/2006-11/msg00225.html

and briefly described in:

http://sourceware.org/ml/gdb-patches/2007-06/msg00315.html

is not.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-09-06 10:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-04 12:53 Vladimir Prus
2007-09-05  5:24 ` Nick Roberts
2007-09-05  5:39   ` Vladimir Prus
2007-09-05  6:25     ` Nick Roberts
2007-09-05 17:27     ` Eli Zaretskii
2007-09-05 18:42       ` Vladimir Prus
2007-09-06  6:46         ` Eli Zaretskii
2007-09-06  7:20           ` Vladimir Prus
2007-09-06  8:12             ` Fabian Cenedese
2007-09-06  8:24               ` Mark Kettenis
2007-09-06 11:39                 ` Nick Roberts [this message]
2007-09-06 21:18               ` Vladimir Prus
2007-09-06 14:38             ` Bob Rossi
2007-09-06 15:06               ` Vladimir Prus
2007-09-06 19:34             ` Eli Zaretskii
2007-09-06 19:38               ` Vladimir Prus
2007-09-07  9:04                 ` Eli Zaretskii
2007-09-07  9:15                   ` Nick Roberts
2007-09-07 10:59                     ` Vladimir Prus
2007-09-07 18:06                       ` Eli Zaretskii
2007-09-07 18:18                         ` Daniel Jacobowitz
2007-09-07 18:24                           ` Eli Zaretskii
2007-09-08  0:30                             ` Daniel Jacobowitz
2007-09-08  3:45                           ` Nick Roberts
2007-09-08  7:21                             ` Daniel Jacobowitz
2007-09-09 20:10                       ` Nick Roberts
2007-09-07  8:11             ` Nick Roberts
2007-09-06 15:03         ` Jim Blandy
2007-09-06 18:08         ` Jim Ingham
2007-09-06 18:34           ` Vladimir Prus
2007-09-06 18:41             ` Jim Ingham
2007-09-06 18:48               ` Vladimir Prus
2007-09-07  5:54                 ` André Pönitz

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=18143.53182.131267.53024@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=Cenedese@indel.ch \
    --cc=gdb@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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