You are not logged in.
I just created my first ABS package from the PKGBUILD available on the AUR: http://aur.archlinux.org/packages/easyt … l/PKGBUILD
Problem is, it has a bug. So I got a backtrace from gdb, sent it along to the author, and got the following response:
This backtrace contains no informations as the binary was probably stripped. Could you recompile EasyTAG from sources to have more information on the crash?
Does ABS/makepkg -i do something funny such that I couldn't get a backtrace? If not, why would he say this?
[img]http://www.archlinux.org/logos/button.png[/img] [img]http://mandrivausers.org/style_emoticons/default/2thumbsup.gif[/img]
Offline
makepkg strips debug symbols. Use makepkg -n to skip stripping. Additionally, you could put "make CFLAGS+=-g" in the PKGBUILD instead of just plain "make", this makes sure line numbers are available in the code, which helps out debugging a lot.
Offline
Excellent; thanks for your help.
[img]http://www.archlinux.org/logos/button.png[/img] [img]http://mandrivausers.org/style_emoticons/default/2thumbsup.gif[/img]
Offline
http://bugzilla.gnome.org/show_bug.cgi?id=308223
So, apparently, for a different bug, I'll need the debugging symbols for more than just the program in question. Is there an easy way to "unstrip" the libraries, or will this involve making new packages for each?
[img]http://www.archlinux.org/logos/button.png[/img] [img]http://mandrivausers.org/style_emoticons/default/2thumbsup.gif[/img]
Offline