Bug#242737: libwxgtk2.4-python: Segfaults on invocation of SetTimeT

2012-05-29 Thread Olly Betts
On Thu, Oct 13, 2011 at 09:10:18AM -0700, Robin Dunn wrote: > SWIG has a problem with methods that return a reference to self, and > it treats the intermediate results as temporaries and creates new > proxies for them. When chaining calls together like that it ends up > thinking that the original

Bug#242737: libwxgtk2.4-python: Segfaults on invocation of SetTimeT

2011-10-13 Thread Robin Dunn
On 10/13/11 4:50 AM, Olly Betts wrote: # I've reproduced this with some recent versions: found 2.8.10.1-3 found 2.8.10.1+dfsg-4 found 2.8.12.1-1 thanks On Fri, Jul 30, 2004 at 07:25:12PM +0930, Ron wrote: I can reproduce this one in 2.4.2.4, in 2.4 branch head, and in 2.5.1. Should he just not

Bug#242737: libwxgtk2.4-python: Segfaults on invocation of SetTimeT

2011-10-13 Thread Olly Betts
# I've reproduced this with some recent versions: found 2.8.10.1-3 found 2.8.10.1+dfsg-4 found 2.8.12.1-1 thanks On Fri, Jul 30, 2004 at 07:25:12PM +0930, Ron wrote: > I can reproduce this one in 2.4.2.4, in 2.4 branch head, and > in 2.5.1. Should he just not be doing this (DateTime() doesn't > r