On Friday 24 June 2011, 03:35:55 Algis Kabaila wrote:
> On Thu, 23 Jun 2011 10:08:50 PM Hans-Peter Jansen wrote:
> > Dear Al,
> >
> > On Thursday 23 June 2011, 13:26:02 Algis Kabaila wrote:
> > > On Thu, 23 Jun 2011 07:06:49 PM Hans-Peter Jansen wrote:
>
> [snip...]
> Following Pete's advise, I've
On Thu, 23 Jun 2011 10:08:50 PM Hans-Peter Jansen wrote:
> Dear Al,
>
> On Thursday 23 June 2011, 13:26:02 Algis Kabaila wrote:
> > On Thu, 23 Jun 2011 07:06:49 PM Hans-Peter Jansen wrote:
[snip...]
Following Pete's advise, I've installed 23 new packages that appeared to be
dbg related (169 MiB d
On Thu, 23 Jun 2011 10:08:50 PM Hans-Peter Jansen wrote:
> Dear Al,
>
> On Thursday 23 June 2011, 13:26:02 Algis Kabaila wrote:
> > On Thu, 23 Jun 2011 07:06:49 PM Hans-Peter Jansen wrote:
> > > On Thursday 23 June 2011, 08:28:06 David Townshend wrote:
> > > > If it vanishes, it implies a segfault
Dear Al,
On Thursday 23 June 2011, 13:26:02 Algis Kabaila wrote:
> On Thu, 23 Jun 2011 07:06:49 PM Hans-Peter Jansen wrote:
> > On Thursday 23 June 2011, 08:28:06 David Townshend wrote:
> > > If it vanishes, it implies a segfault which you will probably see
> > > if you run idle form the command l
On Thu, 23 Jun 2011 07:06:49 PM Hans-Peter Jansen wrote:
> On Thursday 23 June 2011, 08:28:06 David Townshend wrote:
> > If it vanishes, it implies a segfault which you will probably see if
> > you run idle form the command line. You should be able to get a
> > backtrace by running idle through gdb
On Thursday 23 June 2011, 08:28:06 David Townshend wrote:
> If it vanishes, it implies a segfault which you will probably see if
> you run idle form the command line. You should be able to get a
> backtrace by running idle through gdb, i.e, from the command line,
> run "gdb idle". Then in gdb type
If it vanishes, it implies a segfault which you will probably see if you run
idle form the command line. You should be able to get a backtrace by running
idle through gdb, i.e, from the command line, run "gdb idle". Then in gdb
type "run". Idle should start as usual, so get it to crash. Then withi
On Thu, 23 Jun 2011 03:23:36 PM David Townshend wrote:
> On Thu, Jun 23, 2011 at 6:14 AM, Algis Kabaila wrote:
> > On Thu, 23 Jun 2011 08:17:04 AM Baz Walter wrote:
> > > On 22/06/11 20:49, David Townshend wrote:
> > > > On Wed, Jun 22, 2011 at 2:34 PM, Baz Walter wrote:
> > > >> according to the
On Thu, Jun 23, 2011 at 6:14 AM, Algis Kabaila wrote:
> On Thu, 23 Jun 2011 08:17:04 AM Baz Walter wrote:
> > On 22/06/11 20:49, David Townshend wrote:
> > > On Wed, Jun 22, 2011 at 2:34 PM, Baz Walter wrote:
> > >> according to the qt docs, only one application object should be
> created
> > >>
On Thu, 23 Jun 2011 08:17:04 AM Baz Walter wrote:
> On 22/06/11 20:49, David Townshend wrote:
> > On Wed, Jun 22, 2011 at 2:34 PM, Baz Walter wrote:
> >> according to the qt docs, only one application object should be created
> >> at a time, and there is a global qApp pointer which refers to the
>
On 22/06/11 20:49, David Townshend wrote:
On Wed, Jun 22, 2011 at 2:34 PM, Baz Walter wrote:
according to the qt docs, only one application object should be created at
a time, and there is a global qApp pointer which refers to the current
instance.
this suggests that, in pyqt, something like t
On Wed, Jun 22, 2011 at 2:34 PM, Baz Walter wrote:
> On 21/06/11 17:04, David Townshend wrote:
>
>> The problem is that creating (and quitting) multiple QApplications in
>> succession causes a segfault. This situation tends to occur in unit
>> tests,
>> particularly in testing subclasses of QApp
On 21/06/11 17:04, David Townshend wrote:
The problem is that creating (and quitting) multiple QApplications in
succession causes a segfault. This situation tends to occur in unit tests,
particularly in testing subclasses of QApplication.
The following snippet illustrates the problem:
>>> fro
On Tue, Jun 21, 2011 at 11:21 PM, Algis Kabaila wrote:
> On Wed, 22 Jun 2011 02:04:25 AM David Townshend wrote:
> > Hi
> >
> > I'm not sure of the appropriate place to file a PyQt bug report, so I
> hope
> > its ok to send it to this mailing list.
> >
> > The problem is that creating (and quitting
On Wed, 22 Jun 2011 02:04:25 AM David Townshend wrote:
> Hi
>
> I'm not sure of the appropriate place to file a PyQt bug report, so I hope
> its ok to send it to this mailing list.
>
> The problem is that creating (and quitting) multiple QApplications in
> succession causes a segfault. This situ
Hi
I'm not sure of the appropriate place to file a PyQt bug report, so I hope
its ok to send it to this mailing list.
The problem is that creating (and quitting) multiple QApplications in
succession causes a segfault. This situation tends to occur in unit tests,
particularly in testing subclasse
16 matches
Mail list logo
