Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Pedro Alves <palves@redhat.com>,
	Joel Brobecker <brobecker@adacore.com>,
	gdb-patches@sourceware.org
Subject: Re: [patch] Do not open Python scripts twice #2 [Re: [RFC] Crash sourcing Python script on Windows]
Date: Mon, 23 Jan 2012 22:08:00 -0000	[thread overview]
Message-ID: <CADPb22Qn9gKcHkhCSoAwwMbxK45So7iuA20MPZm_tQ_zDkQz-g@mail.gmail.com> (raw)
In-Reply-To: <20120123210850.GA28792@host2.jankratochvil.net>

On Mon, Jan 23, 2012 at 1:08 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Mon, 23 Jan 2012 19:38:34 +0100, Pedro Alves wrote:
>> > +# MS-Windows platform may have Python compiled with different libc
>> > +# having the FILE structure layout incompatible between libraries.
>>
>> It is not just about the layout.  The layout of both libc's could be the
>> same, but you'd still (maybe) crash.  It's more about the private global
>> state maintained by each of the libc's.  E.g., file descriptor N of
>> gdb's libc has no meaning the python's libc -- each libc has its own
>> file descriptor table.
>
> I have updated the text.
>
>
>> This is undefined behavior in the supposedly crashing case.  Hopefully this
>> doesn't happen to succeed by running some other random program.  :-)
>
> Yes, my fear is that if for example the only problem is fd assignments it may
> try to read from a closed descriptor possibly behaving as empty file and it
> would falsely pass.  Better test would be it did really read some test Python
> code but a minimal such testcase looks pretty complicated to me for configure.
> But when Joel was talking about "crash" this simple test may be enough.
>
>
>> The patch looks good to me.
>
> These are the reasons why I would prefer a real MS-Windows test of it.
>
>
> Thanks,
> Jan
>
>
> gdb/
> 2012-01-23  Jan Kratochvil  <jan.kratochvil@redhat.com>
>
>        Do not open script filenames twice.
>        * cli/cli-cmds.c (source_script_from_stream): Pass to
>        source_python_script also STREAM.
>        * config.in: Regenerate.
>        * configure: Regenerate.
>        * configure.ac (HAVE_PYTHON_FILEP_COMPAT): New test.
>        * python/py-auto-load.c (source_section_scripts): Pass to
>        source_python_script_for_objfile also STREAM.
>        (auto_load_objfile_script): Pass to source_python_script_for_objfile
>        also INPUT.
>        * python/python-internal.h (source_python_script_for_objfile): New
>        parameter file, rename parameter file to filename.
>        * python/python.c (python_run_simple_file): Call PyRun_SimpleFile
>        instead if HAVE_PYTHON_FILEP_COMPAT.
>        (source_python_script, source_python_script_for_objfile)
>        (source_python_script): New parameter file, rename parameter file to
>        filename.  Pass FILENAME to python_run_simple_file.
>        * python/python.h (source_python_script): New parameter file, rename
>        parameter file to filename.

Hi.
Do you have any data that shows there is a problem with the double opening?
[I'm kinda uncomfortable with this patch, as is.]


  reply	other threads:[~2012-01-23 22:00 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28 23:24 [RFC] Crash sourcing Python script on Windows Joel Brobecker
2011-09-29  2:00 ` Paul_Koning
2011-09-29  2:19   ` John Spencer
2011-09-29  4:47     ` Joel Brobecker
2011-09-29  7:30       ` Eli Zaretskii
2011-09-29  8:54         ` Kai Tietz
2011-09-29  9:48           ` Eli Zaretskii
2011-09-29  9:51             ` Kai Tietz
2011-09-29 10:54       ` Pedro Alves
2011-09-29 12:33         ` Eli Zaretskii
2011-09-29 12:48           ` Kai Tietz
2011-09-29 13:19           ` Pedro Alves
2011-09-29  7:26     ` Eli Zaretskii
2011-10-03 20:05     ` Tom Tromey
2011-09-29  7:20   ` Eli Zaretskii
2011-10-03 20:02 ` Tom Tromey
2011-10-03 20:53   ` Joel Brobecker
2011-10-04 17:08     ` Tom Tromey
2012-01-23 18:14 ` [patch] Do not open Python scripts twice #2 [Re: [RFC] Crash sourcing Python script on Windows] Jan Kratochvil
2012-01-23 18:41   ` Pedro Alves
2012-01-23 21:55     ` Jan Kratochvil
2012-01-23 22:08       ` Doug Evans [this message]
2012-01-23 22:47         ` Jan Kratochvil
2012-01-23 23:47           ` Doug Evans
2012-01-24 14:45             ` Jan Kratochvil
2012-01-24 18:56               ` Doug Evans
2012-01-24 19:41                 ` Jan Kratochvil
2012-01-24 22:20                   ` Doug Evans
2012-01-24 23:49                     ` Jan Kratochvil
2012-01-25 22:30                       ` Jan Kratochvil
2012-01-26  7:18                         ` Joel Brobecker
2012-01-26 22:03                           ` [commit] " Jan Kratochvil
2012-01-24 15:15             ` Pedro Alves
2012-01-23 19:57   ` Pedro Alves

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=CADPb22Qn9gKcHkhCSoAwwMbxK45So7iuA20MPZm_tQ_zDkQz-g@mail.gmail.com \
    --to=dje@google.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=palves@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