DrKonqi backtrace generation broken with gdb 7.8

[Andreas K. Huettel]

Am Freitag, 10. Oktober 2014, 19:20:21 schrieb Albert Astals Cid:

> > > -Exec=gdb -nw -n -batch -x %tempfile -p %pid %execpath
> > > +Exec=gdb -nw -n -batch -ex "mt set target-async off" -ex "attach
> > > %pid" -x %tempfile %execpath
> > > 
> > >  BatchCommands=set width 200\nthread\nthread apply all bt
> > 
> > Upstream bug: https://sourceware.org/bugzilla/show_bug.cgi?id=17446
> > Upstream commit (probably):
> > https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7ec5670becb3f9
> > 78f 4d2f4df252ad0cbf805e37a
> > 
> > One could also attempt to backport that.
> 
> I'd say that makes more sense than us changing our code because someone
> else introduced a regression.
> 
> Opinions?
> 

A change/backport/patch/update in a core system package is always harder to 
push through on distro level than a corresponding change in a desktop 
environment application.

Please don't rely on the gdb backport.

-- 

Andreas K. Huettel
Gentoo Linux developer 
dilfridge at gentoo.org
http://www.akhuettel.de/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 951 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20141010/9fc1bc08/attachment.sig>