> On Mar 30, 2021, at 10:35 AM, Thiago Macieira via subsurface
> wrote:
>> I wonder why I didn't find this with Valgrind. Given that my professional
>> software developer career started writing a memory debugger 27 years ago...
>> I find Valgrind frustratingly inconsistent to use.
Hmm. A
On Tuesday, 30 March 2021 08:30:31 PDT Dirk Hohndel via subsurface wrote:
> I wonder why I didn't find this with Valgrind. Given that my professional
> software developer career started writing a memory debugger 27 years ago...
> I find Valgrind frustratingly inconsistent to use.
>
> /D
Try ASan
> On Mar 30, 2021, at 12:26 AM, Berthold Stoeger
> wrote:
>
> On Dienstag, 30. März 2021 05:32:37 CEST Dirk Hohndel via subsurface wrote:
>> The consistent trigger appears to be closing a dive file. My guess is that
>> some destructor gets called twice or that in some other way we access
On Dienstag, 30. März 2021 05:32:37 CEST Dirk Hohndel via subsurface wrote:
> The consistent trigger appears to be closing a dive file. My guess is that
> some destructor gets called twice or that in some other way we access freed
> memory.
>
> I tried to figure this out by starting at valgrind
The consistent trigger appears to be closing a dive file. My guess is that some
destructor gets called twice or that in some other way we access freed memory.
I tried to figure this out by starting at valgrind output on Linux, but so far
I haven't managed to figure it out...
Help with this one
On 30 October 2014 00:07, Dirk Hohndel d...@hohndel.org wrote:
Please test
http://subsurface-divelog.org/downloads/daily/subsurface-4.2-349-g2b8043b82b99.exe
if you have a chance to make sure that it's not just my system where this
works again...
This one also implements the long missing
On Oct 30, 2014, at 3:15 AM, Lubomir I. Ivanov neolit...@gmail.com wrote:
On 30 October 2014 00:07, Dirk Hohndel d...@hohndel.org wrote:
Please test
http://subsurface-divelog.org/downloads/daily/subsurface-4.2-349-g2b8043b82b99.exe
if you have a chance to make sure that it's not just my
On Wed, Oct 29, 2014 at 09:19:22PM -0700, Dirk Hohndel wrote:
On Oct 29, 2014, at 6:50 PM, Thiago Macieira thi...@macieira.org wrote:
I'm fairly certain it's not a Qt bug now. This is a binary incompatibility
issue between QtGui and QtWidgets due either a bug in Dirk's packaging or
On Wed, Oct 29, 2014 at 6:38 PM, Dirk Hohndel d...@hohndel.org wrote:
Running my latest daily build (not on the server, yet, for obvious
reasons) I get the following crash. And I have no clue how to read
those...
Problem signature:
Problem Event Name: APPCRASH
On Wed, Oct 29, 2014 at 06:46:12PM -0200, Tomaz Canabrava wrote:
On Wed, Oct 29, 2014 at 6:38 PM, Dirk Hohndel d...@hohndel.org wrote:
Running my latest daily build (not on the server, yet, for obvious
reasons) I get the following crash. And I have no clue how to read
those...
On Wed, Oct 29, 2014 at 01:52:07PM -0700, Dirk Hohndel wrote:
I remember this rat hole. My Qt libraries come from Fedora (cross built
for Win64). A debug build of Marble alone is several hundred megabytes and
takes roughly forever... and I have yet to be able to build a single
installer that
On Wed, Oct 29, 2014 at 7:04 PM, Dirk Hohndel d...@hohndel.org wrote:
On Wed, Oct 29, 2014 at 01:52:07PM -0700, Dirk Hohndel wrote:
I remember this rat hole. My Qt libraries come from Fedora (cross built
for Win64). A debug build of Marble alone is several hundred megabytes
and
takes
On Wednesday 29 October 2014 15:07:35 Dirk Hohndel wrote:
I have no debug symbols. Thiago is looking into this and he came to the
conclusion that this might be a Qt 5.3.2 bug. The previous Fedora version
was 5.3.1 - but I can't get those RPMs anymore.
I'm fairly certain it's not a Qt bug now.
13 matches
Mail list logo
