From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] python: load *-gdb.py for shlibs during attach
Date: Wed, 22 Sep 2010 20:09:00 -0000 [thread overview]
Message-ID: <m3hbhh7ehs.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100922192633.GA29052@host1.dyn.jankratochvil.net> (Jan Kratochvil's message of "Wed, 22 Sep 2010 21:26:33 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> BTW what do you think about the case when the called python scripts would
Jan> manipulate the ALL_OBJFILES list? But even ALL_OBJFILES_SAFE would not be
Jan> safe enough in such case.
I'm inclined not to worry about it.
I guess we could come up with a scheme to make it work. That seems like
a lot of effort for something that, at present, is just a theoretical
problem.
Tom
next prev parent reply other threads:[~2010-09-22 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 16:20 Jan Kratochvil
2010-09-22 19:41 ` Tom Tromey
2010-09-22 19:51 ` Jan Kratochvil
2010-09-22 20:09 ` Tom Tromey [this message]
2010-09-22 21:33 ` Jan Kratochvil
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=m3hbhh7ehs.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).