Arch Linux

krelian

Member

Registered: 2009-07-18

Posts: 1

General advice about fixing bugs and contributing

I use Archlinux and KDE. Let's say I have found a bug in one of the KDE apps (let's say kcalc) which I would like to take a closer look at. How would I go about building a version of this app with debug symbols without affecting the general usability of my Archlinux installation? How can I easily revert back?

I am specifically using a KDE app as an example because it's a large and complicated project. If it was just a standalone app
things would be much simpler and the chance of messing up my day to day system is much smaller.

I am asking this because I have found out (and please correct me if you think I am wrong) that in order to squash bugs in an application you are not familiar
with (and even just to provide a helpful bug report) a debug build is almost mandatory and I am trying to understand what would be the most hassle free
way to do that.

What is you workflow when trying to investigate a bug in a program you use but are not really part of the dev team?

Thanks ahead.

ngoonee

Forum Fellow

From: Between Thailand and Singapore

Registered: 2009-03-17

Posts: 7,358

Re: General advice about fixing bugs and contributing

Modify the PKGBUILD? Most programs I know off I just file the bug first, will do a debug build of a specific component if requested by the devs.

For example, a problem with Evolution's calendar. I was asked to patch both evo and evo-data-server, so i just modify the PKGBUILD for both those, install the new package (the old one is of course in my cache), test, and reinstall the 'stock' ones.

---

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

grey

Member

From: Europe

Registered: 2007-08-23

Posts: 679

Re: General advice about fixing bugs and contributing

As long as you use pacman to install the application it should be safe as easy to roll-back.

FWIW my workflow is:
1. make sure ~/.makepkg.conf has debug flags on and strip disabled
2. makepkg
3. pacman -U

Then start gdb and inspect / modify the sources. To check one of your modifications:

3. cd src/$pkgname-$pkgver
4. build manually or by replicating the instructions in the PKGBUILD file. Skip the patches.
5. modify the PKGBUILD so that the build() function only does installation.
6. makepkg -ef
7. pacman -U

---

Good ideas do not need lots of lies told about them in order to gain public acceptance.

tavianator

Member

From: Waterloo, ON, Canada

Registered: 2007-08-21

Posts: 859

Website

Re: General advice about fixing bugs and contributing

Um, why install the debug build at all?  Just compile it (with cmake && make; makepkg is not even necessary), and run the kcalc you just compiled.