Help Locating Base Code
jmadero.dev at gmail.com
Mon Aug 20 09:53:38 PDT 2012
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 but hours upon hours of trying to find the code has left me a
On Thu, Aug 9, 2012 at 10:34 AM, Joel Madero <jmadero.dev at gmail.com> wrote:
> 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.
> On Wed, Aug 8, 2012 at 11:49 PM, Jan Holesovsky <kendy at suse.cz> wrote:
>> 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 crashed, do 'bt' in gdb - that will show you backtrace
>> of the crash. If it looks unrelated, do 'thread apply all bt' which
>> will show backtrace of all threads.
>> > Not sure why. Also mine looks nothing like Lionel's did when he ran gdb.
>> > Mine looks more like this:
>> After issuing 'bt' (Lionel's "and look at the backtrace"), you should
>> see something similar to Lionel's output :-)
>> All the best,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the LibreOffice