Would somebody running a recent GIT please confirm whether they can
create
a backtrace with DrKonqi?
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.
Which patch is that? I'm testing this on Slackware 13.1, which uses glibc 2.11.1, kernel 2.6.33.x. I don't think any such patch is part of 13.1.
It very well may not be--here's the Ubuntu patch and security discussion: https://wiki.ubuntu.com/Security/Features#ptrace
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.
Perhaps provide me the exact steps you want to me follow to test gdb. That is, last week when I could not start konqueror, just after the tdelibs ABI patch, I created a backtrace like this:
gdb -- arg konqueror run bt
If that is sufficient, then drkonqi is broken?
The steps I was thinking were these: 1.) Start a TDE process, noting its PID 2.) Run gdb 3.) attach <pid>
If you see a bunch of debugging symbols being loaded then gdb is working fine, and DrKonqui is broken. If gdb spits out an error, then something else has gone wrong.
Tim