21 May
2012
21 May
'12
1:40 a.m.
Using recent GIT sources, does DrKonqi work correctly
to create
backtraces?
When I run crashtest in 3.5.10, DrKonqi creates a backtrace. In TDE all I
get is the following message:
"This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents
creation of proper backtraces, or the stack frame was seriously corrupted
in the crash."
This worked some time in the past (I am the one who patched tdebase so
crashtest would build).
My build scripts all use --enable-debug=full for automake and -ggdb for
cmake. The build logs show that the packages are compiling with those
flags and the increased package sizes are further evidence.
Yet I can't create a backtrace through DrKonqi. The crashtest binary
should be sufficient to test DrKonqi.
Would somebody running a recent GIT please confirm whether they can create
a backtrace with DrKonqi?
Thanks.
Darrell
No luck here, but then again gdb isn't working for me either.
I would verify that we aren't getting bit by the ptrace security patch
that was applied to Ubuntu some time ago, and may be filtering into other
distributions by now. See if you can attach to a process with gdb as a
normal user--if you can, and DrKonqui still doesn't work, then we have a
problem.
Tim