On Wed, Aug 22, 2012 at 08:20:45AM -0700, Joel Madero wrote:
> Thanks for letting me know it's Lionel :)
In general, you can find "subject-specific experts" listed at
http://wiki.documentfoundation.org/FindTheExpert
> I told Rafael yesterday in the chat that just because I enjoy being
> angry (a
On Wed, Aug 22, 2012 at 09:21:24AM +0100, Mark Stanton wrote:
>> Oh - database expert, that's Lionel :-) But of course, having more
>> database experts would be great!
> I intended that to be me. Having spent more than twenty years
> writing them I thought I might qualify.
Cool! I'm already re
Thanks for letting me know it's Lionel :) I told Rafael yesterday in the
chat that just because I enjoy being angry (actually just enjoy a good
challenge) I'll probably assign myself another base bug in the coming weeks
and spend 20 hours to fix one line ;) now I know who to bug with every
minor qu
> Oh - database expert, that's Lionel :-) But of course, having more
> database experts would be great!
I intended that to be me. Having spent more than twenty years writing
them I thought I might qualify.
I'm reading the lists (here, dev & qa) regularly, but unfortunately at
the moment I'm
Hi Joel,
On 2012-08-21 at 11:10 -0700, Joel Madero wrote:
> Thanks to everyone who helped me along the way. The code actually
> ended up being in formcomponenthandler.cxx,
> FormComponentPropertyHandler::impl_browseImage_nothrow.
Great to hear; I hope I did not mislead you too much - that was t
Thanks to everyone who helped me along the way. The code actually ended up
being in formcomponenthandler.cxx,
FormComponentPropertyHandler::impl_browseImage_nothrow.
One simple change and it's good. Many thanks to everyone again, Rafael
ended up locating the exact location and helping me see what
On Tue, Aug 21, 2012 at 11:58:15AM +0200, Jan Holesovsky wrote:
> On 2012-08-20 at 09:53 -0700, Joel Madero wrote:
>> I am still having a hard time locating the relevant code for this bug
>> fdo#53001. I did the backtrace with the dialog open and I didn't see
>> anything useful in there. If someo
Hi Joel,
On 2012-08-20 at 09:53 -0700, Joel Madero wrote:
> I am still having a hard time locating the relevant code for this bug
> fdo#53001. I did the backtrace with the dialog open and I didn't see
> anything useful in there. If someone can help direct me to the
> relevant code OR if someone i
I am still having a hard time locating the relevant code for this bug
fdo#53001. I did the backtrace with the dialog open and I didn't see
anything useful in there. If someone can help direct me to the relevant
code OR if someone is willing to take the bug and fix it, I think it's a 20
minute fix b
Thanks to everyone. I have successfully done my first backtrace :) It was
unrelated but I see things that make sense :) now time to try to locate
this dialog and the trigger that is affecting image linking.
Joel
On Wed, Aug 8, 2012 at 11:49 PM, Jan Holesovsky wrote:
> Hi Joel,
>
> Joel Madero
Hi Joel,
Joel Madero píše v St 08. 08. 2012 v 18:35 -0700:
> Thanks for the advice. Unfortunately every time I run "run" and get into
> database I get a segfault in gdb.
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffc2d06700 (LWP 4977)]
To see where it c
On Wed, Aug 08, 2012 at 06:35:18PM -0700, Joel Madero wrote:
> On 08/08/2012 06:01 AM, Michael Meeks wrote:
>> On Wed, 2012-08-08 at 07:32 +0200, Lionel Elie Mamane wrote:
>>> On Tue, Aug 07, 2012 at 06:50:22PM -0700, Joel Madero wrote:
I'm trying to locate the code that handles the dialog th
On 08/08/2012 06:01 AM, Michael Meeks wrote:
On Wed, 2012-08-08 at 07:32 +0200, Lionel Elie Mamane wrote:
On Tue, Aug 07, 2012 at 06:50:22PM -0700, Joel Madero wrote:
I'm trying to locate the code that handles the dialog that appears when you
do the following steps in base:
To answer this kind
After that, to execute the program you need to type run and press enter
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
On 08/08/2012 11:34 AM, Jan Holesovsky wrote:
gdb ./soffice.bin
when I do that all I get is this:
joel@joel-Studio-1737:/data/git/libo/install/program$ gdb ./soffice.bin
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GN
Hi Joel,
On 2012-08-08 at 08:24 -0700, Joel Madero wrote:
> 1. For getting a bit more in depth instructions, is it best to ask
> here or in IRC? I believe (almost positive) that my Libo is installed
> with symbols enabled, so I want to try to do the gdb method but need
> kind of a complete breakd
Thanks to both of you. I have tried the gdb method before and honestly, for
a new programmer, our directions aren't the best on the wiki. I am yet to
successfully make progress but I am going to figure it out this time around
since it seems like that's what is needed. Usually I just grep the label
On Wed, Aug 08, 2012 at 02:01:28PM +0100, Michael Meeks wrote:
> On Wed, 2012-08-08 at 07:32 +0200, Lionel Elie Mamane wrote:
>> On Tue, Aug 07, 2012 at 06:50:22PM -0700, Joel Madero wrote:
>>> I'm trying to locate the code that handles the dialog that appears when you
>>> do the following steps i
On Wed, 2012-08-08 at 07:32 +0200, Lionel Elie Mamane wrote:
> On Tue, Aug 07, 2012 at 06:50:22PM -0700, Joel Madero wrote:
> > I'm trying to locate the code that handles the dialog that appears when you
> > do the following steps in base:
>
> To answer this kind of questions, I find it useful to
On Tue, Aug 07, 2012 at 06:50:22PM -0700, Joel Madero wrote:
> I'm trying to locate the code that handles the dialog that appears when you
> do the following steps in base:
To answer this kind of questions, I find it useful to run a build with
symbols (debug build) under gdb. Then, when the dialo
Hi All,
Spent a few hours trying to track this down and I can't figure it out so
hoping someone can guide me in the right direction.
I'm trying to locate the code that handles the dialog that appears when you
do the following steps in base:
1. From Start Center create and save new "sample.odb"
2
21 matches
Mail list logo