976880 - gdb not installed in idle-mock-hw

Status: VERIFIED FIXED

(Release Engineering :: General, defect)

Description

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

It will be nice to have gdb installed on idle-mock-hw, to get crash dumps when issues are hit.

Comment 1

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Yes, gdb is indeed not installed, as I checked:

Exception("'No such file or directory' error calling: gdb --version",)

Comment 2

[Chris Cooper [:coop] (he/him)]

(In reply to Gary Kwong [:gkw] [:nth10sd] from comment #1)
> Yes, gdb is indeed not installed, as I checked:
> 
> Exception("'No such file or directory' error calling: gdb --version",)

Expected...we don't generally install debugging tools on the build slaves by default since they aren't used for dev. We can certainly get it installed on the hardware slaves for this though.

Still looking for someone to pick this up.

Comment 3

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

It is tremendously helpful to have gdb installed, for the fuzzing harness.

The old machines had gdb installed - since :coop is away, bhearsum/armenzg, may I know what is needed to get it done?

Comment 4

[Armen [:armenzg]]

1) Request a loaner machine, install gdb and test that it does that you need
2) Write a puppet patch to install gdb
2.b) If this requires a DEB file this will be needed to create it [1]
3) Test the puppet change on a machine and let it take one of the jobs you care about (I assume fuzzing)
4) Deploy wide-spread

I don't currently have time for this. I'm just laying down the path to success.

[1] https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain/HowTo/Build_DEBs

Comment 5

[[e-mail] (:bhearsum)]

Attachment: add-gdb-to-mock.diff

(In reply to Armen Zambrano [:armenzg] (Release Engineering) (EDT/UTC-4) from comment #4)
> 1) Request a loaner machine, install gdb and test that it does that you need
> 2) Write a puppet patch to install gdb
> 2.b) If this requires a DEB file this will be needed to create it [1]
> 3) Test the puppet change on a machine and let it take one of the jobs you
> care about (I assume fuzzing)
> 4) Deploy wide-spread
> 
> I don't currently have time for this. I'm just laying down the path to
> success.
> 
> [1] https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain/HowTo/Build_DEBs

I don't think this is relevant. These jobs run on RPM-based platforms, and we have gdb available: http://releng-puppet2.srv.releng.scl3.mozilla.com/repos/yum/mirrors/centos/6/latest/os/x86_64/gdb-7.2-50.el6.x86_64.rpm

Despite the name, they don't appear to run inside of a mock environment though, so they'll need to be installed in the base system.

I agree with Coop that it's not ideal to install gdb on the base system, I don't think it's the type of thing that will cause problems.

Comment 6

[[e-mail] (:bhearsum)]

Comment on attachment 8391173 [details] [diff] [review]
add-gdb-to-mock.diff

Landed this on default+production. Should take effect for new jobs starting in 30min-1h.

Comment 7

[[e-mail] (:bhearsum)]

Had to land a follow-up to change the version to 7.2-50.el6 -- apparently Puppet is fussier than the command-line yum tool. Seems to be fine now:
[[e-mail] ~]# gdb
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-50.el6)

Comment 8

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Thanks all! I've verified that gdb now shows up correctly:

gdb version: GNU gdb (GDB) Red Hat Enterprise Linux (7.2-50.el6)