Hi Alan,
Alan W. Irwin wrote:
> On 2009-03-13 14:20- Andrew Ross wrote:
> Hi Alban:
>
> Earlier today (revision 9765) I applied your patch that introduces a mutex
> with the goal of making the qt device driver thread safe. With this change
> issue (1) seems to be addressed, and no new issues
On 2009-03-13 14:20- Andrew Ross wrote:
> On Fri, Mar 13, 2009 at 01:58:18PM +, Alban Rochel wrote:
>> Andrew Ross wrote:
>>> It does however fix things for me and ctest again runs successfully.
>>>
>>> Andrew
>>>
>>
>> I'm glad you managed to fix this. Thanks a lot!
>>
>> Alban
>
> No pro
On 2009-03-14 19:11- Andrew Ross wrote:
> On Fri, Mar 13, 2009 at 04:45:45PM -0700, Alan Irwin wrote:
>> Hi Andrew:
>>
>> I frankly don't understand the differing results that we had, and that
>> bothers me. In particular I don't understand why you had memory management
>> problems for the ve
On Fri, Mar 13, 2009 at 04:45:45PM -0700, Alan Irwin wrote:
> Hi Andrew:
>
> I frankly don't understand the differing results that we had, and that
> bothers me. In particular I don't understand why you had memory management
> problems for the versions prior to your recent commit while I did not
Alan W. Irwin writes:
> However, I still don't understand why valgrind reported no issues on my
> platform without your recent changes. Segfaults can come and go (although
> usually a segfault does show up for one of our 31 examples if there is a
> memory management issue with the device drive
On 2009-03-13 13:54- Andrew Ross wrote:
> On Fri, Mar 13, 2009 at 11:19:08AM +, Alban Rochel wrote:
>> Andrew Ross wrote:
>>> On Fri, Mar 13, 2009 at 09:25:43AM +, Alban Rochel wrote:
Andrew Ross wrote:
>>>
>>> This is interesting - we're running exactly the same system, but mine
On Fri, Mar 13, 2009 at 01:58:18PM +, Alban Rochel wrote:
> Andrew Ross wrote:
> > It does however fix things for me and ctest again runs successfully.
> >
> > Andrew
> >
>
> I'm glad you managed to fix this. Thanks a lot!
>
> Alban
No problem. You may want to test use of multiple devices
Andrew Ross wrote:
> It does however fix things for me and ctest again runs successfully.
>
> Andrew
>
I'm glad you managed to fix this. Thanks a lot!
Alban
--
Apps built with the Adobe(R) Flex(R) framework and Flex B
On Fri, Mar 13, 2009 at 11:19:08AM +, Alban Rochel wrote:
> Andrew Ross wrote:
> > On Fri, Mar 13, 2009 at 09:25:43AM +, Alban Rochel wrote:
> >> Andrew Ross wrote:
> >
> > This is interesting - we're running exactly the same system, but mine is
> > on a 32-bit machine. Perhaps this is a
Andrew Ross wrote:
> On Fri, Mar 13, 2009 at 09:25:43AM +, Alban Rochel wrote:
>> Andrew Ross wrote:
>
> This is interesting - we're running exactly the same system, but mine is
> on a 32-bit machine. Perhaps this is a 32-bit / 64-bit issue?
>
> Andrew
Andrew,
I cannot reproduce this bug o
On Fri, Mar 13, 2009 at 09:25:43AM +, Alban Rochel wrote:
> Andrew Ross wrote:
> > On Thu, Mar 12, 2009 at 05:13:11PM -0700, Alan Irwin wrote:
> > My results were with 9730 so included Alban's fixes and I still see
> > the memory management issues with familying on my Kubuntu Intrepid
> > syste
On Fri, Mar 13, 2009 at 09:10:16AM +, Andrew Ross wrote:
>
> My results were with 9730 so included Alban's fixes and I still see
> the memory management issues with familying on my Kubuntu Intrepid
> system (current stable release).
>
> With the current svn revision (r9732) I am getting
> ***
Andrew Ross wrote:
> On Thu, Mar 12, 2009 at 05:13:11PM -0700, Alan Irwin wrote:
> My results were with 9730 so included Alban's fixes and I still see
> the memory management issues with familying on my Kubuntu Intrepid
> system (current stable release).
>
> With the current svn revision (r9732) I
On Thu, Mar 12, 2009 at 05:13:11PM -0700, Alan Irwin wrote:
> On 2009-03-12 20:21- Andrew Ross wrote:
>
> >
> > With current svn all the qt file devices produce a segfault when
> > run with more than one page of output, e.g. example 2. This happens
> > with ctest, or if calling the examples di
On 2009-03-12 20:21- Andrew Ross wrote:
>
> With current svn all the qt file devices produce a segfault when
> run with more than one page of output, e.g. example 2. This happens
> with ctest, or if calling the examples direct, e.g.
> ./x02c -fam -dev bmpqt -o test.bmp
> [...]This happens afte
With current svn all the qt file devices produce a segfault when
run with more than one page of output, e.g. example 2. This happens
with ctest, or if calling the examples direct, e.g.
./x02c -fam -dev bmpqt -o test.bmp
The backtrace is something like
*** glibc detected *** ./x02c: munmap_chunk()
16 matches
Mail list logo
