This is the mail archive of the
mailing list for the GDB project.
Re: [RFC] Crash sourcing Python script on Windows
- From: Tom Tromey <tromey at redhat dot com>
- To: John Spencer <maillist-gdbpatches at barfooze dot de>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 03 Oct 2011 14:05:09 -0600
- Subject: Re: [RFC] Crash sourcing Python script on Windows
- References: <email@example.com> <09787EF419216C41A903FD14EE5506DD03098D555B@AUSX7MCPC103.AMER.DELL.COM> <4E83D440.firstname.lastname@example.org>
>>>>> "John" == John Spencer <email@example.com> 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
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.