On 01/10/2014 10:15 AM, Alex McMurchy wrote:
Though it does seem a bit bizarre that setting up CFLAG external to
autogen.sh can overwrite the internally generated CFLAG, i'd have
thought it should have concatenated the two - is this a bug?
I think it is by design (but personally have lost track
It was something I'd done!
On 28th December 2013, in a separate post,I reported this -
> It seems I may have became a victim of a regression in gcc
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58864 which helped me with this
> statement -
>
> "it breaks with -march=i686 but works with -march=i
On 01/09/2014 11:50 AM, Alex McMurchy wrote:
All this seems to suggest that I haven't compiled correctly to get the
best out of gdb. I've only ever used --enable-dbgutil flag and compiled with
Yes, looks like missing debug information, but --enable-dbgutil should
provide that. No idea what's
Stephan
Thanks for the reply. I'm now thinking I've got something more fundamental
wrong, other than where it's stopped.
Luckily I've not deleted what I did last year - when I was happily using gdb. A
backtrace gives these results -
* #0 0xb73be8ca in poll () from /lib/libc.so.6
*
On 01/08/2014 05:12 PM, Alex McMurchy wrote:
This is what I get towards the back end of gdb when assigning it to a running
soffice.bin -
Reading symbols from
/home/libreoffice/Downloads/core/instdir/ure/lib/libreflectionlo.so...done.
Loaded symbols for
/home/libreoffice/Downloads/core/instdir/ur
After a successful autogen with the --enable-dbgutil flag set and a successful
make, I can't seem to get gdb to debug libreoffice.
I've probably done something silly or missed out something obvious as I've
never had problems before in running gdb against Libreoffice.
I've tested gdb against a
