Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: Multiprocess GDB, formal spec
Date: Fri, 22 Aug 2008 13:17:00 -0000	[thread overview]
Message-ID: <m3abf6jfpo.fsf@fleche.redhat.com> (raw)
In-Reply-To: <48A35D22.30705@codesourcery.com> (Stan Shebs's message of "Wed\, 13 Aug 2008 15\:16\:02 -0700")

>>>>> "Stan" == Stan Shebs <stan@codesourcery.com> writes:

Stan> set args <arg> ...
Stan> set environment <arg> ...

It occurred to me today that "set target-charset" will also have to be
per-inferior.

I am not sure if you were trying to make an exhaustive list here or
not, but figured it was better to mention it than not.

Note that this has some weird implications.  Suppose you are debugging
two running instances of "program", each with a different target
charset.  And suppose you set a breakpoint somewhere in that program,
and that breakpoint's condition uses a string.

Right now, gdb converts to the target charset early -- while parsing.
However, in this case, you would actually want to do the conversion
lazily.  (Lazy would be better anyhow, since target-charset can be
changed by the user at any time.)

These are rather obscure scenarios.

Tom


  parent reply	other threads:[~2008-08-21 20:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14 16:24 Stan Shebs
2008-08-15 13:13 ` Tom Tromey
2008-08-15 15:02   ` Stan Shebs
2008-08-22 13:17 ` Tom Tromey [this message]
2008-10-20 15:30 Marc Khouzam
2008-10-20 15:39 ` Joel Brobecker
2009-12-03 14:59   ` Marc Khouzam
2009-12-03 15:05   ` Marc Khouzam
2009-12-03 15:20     ` Christopher Faylor
2008-10-20 15:53 ` Stan Shebs
2008-10-20 16:23   ` Marc Khouzam
2008-10-31 19:13   ` Marc Khouzam
2008-10-31 19:57     ` Stan Shebs

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=m3abf6jfpo.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=stan@codesourcery.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