. Feel free to
edit/improve the wiki :-)
Another thing about gdb is that breakpoints on C++ functions have
traditionally not work out that well for me; there is always some
gotcha: two forms of object constructor, polymorphic methods,
tab-completion not working / and/or taking forages.
On 06/20/2012 02:04 PM, Joel Madero wrote:
Thanks I'll look through those links. One thing I noticed on the wiki
is that it says to do this:
cd /opt/libreoffice/program
when I install from source it never installs there so I was confused
for a second (or two). I think maybe updating the wiki
Thanks I'll look through those links. One thing I noticed on the wiki is
that it says to do this:
cd /opt/libreoffice/program
when I install from source it never installs there so I was confused for a
second (or two). I think maybe updating the wiki to include a couple
examples or at least a lin
On 06/20/2012 01:45 PM, Daniel Bankston wrote:
Also take a lot at this about gdb and libo if you haven't already:
https://wiki.documentfoundation.org/Development/How_to_debug
Take a "look". :-)
___
LibreOffice mailing list
LibreOffice@lists.freedeskt
On 06/20/2012 01:42 PM, Daniel Bankston wrote:
On 06/20/2012 12:55 PM, Joel Madero wrote:
I think this is a basic question but how do I go about putting on
breakpoints and then how do I "use" the breakpoints to determine
things like what variables are being called on? This st
On 06/20/2012 12:55 PM, Joel Madero wrote:
I think this is a basic question but how do I go about putting on
breakpoints and then how do I "use" the breakpoints to determine
things like what variables are being called on? This stems from a
previous email where someone suggested
I think this is a basic question but how do I go about putting on
breakpoints and then how do I "use" the breakpoints to determine things
like what variables are being called on? This stems from a previous email
where someone suggested doing the following to locate rotating text:
*...Or
Hi Niklas,
On Tuesday, 2011-11-29 09:50:26 +0100, Niklas Johansson wrote:
> >- rList.reset();
> >+ rList.clear();
> >
> >Please check if that fixes the problem.
>
> That fixes the problem, and definitely looks like a cleaner
> solution. Do you create the patch or should I create a new
:00:00 2001
From: Niklas Johansson
Date: Tue, 29 Nov 2011 09:32:14 +0100
Subject: [PATCH] Fixes pass count in Manage Breakpoints
When entering pass count 2 it is expected that the breakpoint is
passed two times before breaking not to break the second time.
---
basctl/source/basicide/baside2.cxx |
Hi Niklas,
On Monday, 2011-11-28 12:27:16 +0100, Niklas Johansson wrote:
> In worst case it makes the program crash. This fix, stores
> the values. I'm not that experienced with C++ so could someone have
> a second look at this there might very well be a "cleaner" way of
> writing it.
Good find!
I started out trying to fix fdo 42778 and noticed that my initial
description of the problem was a bit to narrow. It wasn't just the pass
count that wasn't stored correctly but the breakpoints all together. In
worst case it makes the program crash. This fix, stores the values. I
11 matches
Mail list logo