From: Tom Tromey <tromey@redhat.com>
To: John Spencer <maillist-gdbpatches@barfooze.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Crash sourcing Python script on Windows
Date: Mon, 03 Oct 2011 20:05:00 -0000 [thread overview]
Message-ID: <m3zkhhrgcq.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4E83D440.6000702@barfooze.de> (John Spencer's message of "Thu, 29 Sep 2011 04:13:20 +0200")
>>>>> "John" == John Spencer <maillist-gdbpatches@barfooze.de> writes:
John> FILE is supposed to be an opaque type and as such noone except of the
John> libc which defines it is supposed to "poke" at its internals.
Which is exactly what GDB does.
John> however it is common practice in GNU software to assume everybody uses
John> GLIBC and poke around in internal stuff thats not supposed to be
John> accessibly at all in userland. another example of such illegal
John> behaviour is libevent, which does illegal things with fd_set internals
John> to allow more than FD_SETSIZE file descriptors to be used with
John> select().
I don't even know what libevent is. It isn't part of gdb.
I'm guessing you are referring back to the libthread_db discussion.
If so, please separate the streams. Thanks.
Tom
next prev parent reply other threads:[~2011-10-03 20:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 23:24 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 [this message]
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
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=m3zkhhrgcq.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=maillist-gdbpatches@barfooze.de \
/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