On Thu, Jun 18, 2009 at 09:18:33AM +0200, subhuman wrote: > On Wed, 17 Jun 2009 14:54:02 +0200 > Patrik Fimml <pat...@fimml.at> wrote: > > I can only guess that abiword probably didn't print the document in > > question for you, then. But in your console-output snippet, I do not see > > anything crash-related. No abort, no segfault. What makes you think it's > > a crash? > > When I call abiword from the shell and try to print the document > interactively I find the message "Aborted" after the mysterious > disappearance of abiword. Else (when called from the shell to print) > the snippet I sent is everything I get.
Alright, the absence of the "Aborted" line seemed strange.
> > In addition, please check whether you find the bug to persist in abiword
> > SVN. If it does, and it is a crash, then please compile with debugging
> > symbols and attach a backtrace.
>
> I downloaded version 2.7.4 yesterday from abisource.com. Will this be
> ok for you? Or how can I reach the SVN repository? (However I'm not
> good in CVS/ SVN, so I should prefer a tarball.)
I think 2.7.4 should be recent enough.
Please configure it with
CFLAGS="-g" CXXFLAGS="-g" ./configure --prefix=/tmp/abiword-2.7.4-inst
--disable-gnomeui --disable-gnomevfs
The --prefix is arbitrary, but be sure to install it somewhere and not
run abiword out of the source tree, as it won't find its glade files
otherwise.
Please also install the libgtk2.0-0-dbg and libglib2.0-0-dbg packages.
Then, run it in gdb and get a full backtrace of all threads.
$ gdb /tmp/abiword-2.7.4-inst/bin/abiword
(gdb) set logging on
(gdb) set pagination off
(gdb) run
<reproduce abort>
(gdb) thread apply all bt full
(and attach gdb.txt)
Kind regards,
Patrik
signature.asc
Description: Digital signature
