please add an Architecture: field

Bug #87424 reported by David Farning
6
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Fix Released
Low
Martin Pitt

Bug Description

Binary package hint: apport

Again a another RFE from the mozillateam;) We are having trouble identifying if packages and systems are 32 or 64 bits. It would be very helpful if apport could return that information automatically. John at <email address hidden> is our team members working on these issues. This information is probably general enough to be included in apport rather than as a package hook.

thanks
David Farning

Revision history for this message
Brian Murray (brian-murray) wrote :

Isn't the system architecture information in the uname line of the initial crash? Here is an example: 'Uname: Linux mlenz-laptop 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux'.

Revision history for this message
Kees Cook (kees) wrote : Re: [Bug 87424] Re: unable to tell the difference between 32 and 64 bit builds

On Fri, Feb 23, 2007 at 11:29:30PM -0000, Brian Murray wrote:
> Isn't the system architecture information in the uname line of the
> initial crash? Here is an example: 'Uname: Linux mlenz-laptop
> 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux'.

For 32bit, it will say "i686", and for 64, it will say "x86_64". e.g.,
my machine:

Linux gorgon 2.6.20-8-generic #2 SMP Tue Feb 13 01:14:41 UTC 2007 x86_64
GNU/Linux

Or just uname -m

--
Kees Cook @outflux.net

Revision history for this message
Kees Cook (kees) wrote : Re: unable to tell the difference between 32 and 64 bit builds

Another indicator is in the "Registers.txt". eax is 32, and rax is 64 bit.

Revision history for this message
John Vivirito (gnomefreak) wrote :

I have never seen the x86_64 but i will recheck some. ive seen smp and i686 ty and i will look at a few.

Revision history for this message
Martin Pitt (pitti) wrote :

Indeed an Architecture: field makes sense, especially for multiarch (e. g. running 32 bit firefox on amd64)

Changed in apport:
assignee: nobody → pitti
importance: Undecided → Low
status: Unconfirmed → In Progress
Martin Pitt (pitti)
Changed in apport:
status: In Progress → Fix Committed
Revision history for this message
David Farning (dfarning) wrote : Re: [Bug 87424] Re: please add an Architecture: field

On Mon, 2007-02-26 at 17:35 +0000, Martin Pitt wrote:
> ** Changed in: apport (Ubuntu)
> Status: In Progress => Fix Committed
>

You rock!

thanks
--
David Farning <email address hidden>

Revision history for this message
Martin Pitt (pitti) wrote :

apport (0.60) feisty; urgency=low

  * gtk/apport-gtk.glade: Reintroduce window titles. Since the crash
    notifications are like alerts, title have been removed recently to comply
    with Gnome HIG standards, but then the user will get 'nameless window'
    buttons in the task bar. Let's have the smaller evil then. (LP: #87164)
  * apport/packaging.py: Add get_architecture() interface for determining the
    architecture of a particular package (which might not match the overall
    system architecture on multiarch-capable systems, e. g. an i386 Firefox
    package installed on amd64).
  * backends/packaging-dpkg.py: Implement get_architecture() and add test
    case.
  * apport/report.py, add_package_info(): Add Architecture: field.
    (LP: #87424)
  * apport/ui.py: Already mark report as seen when we load it, not just in the
    information collection thread. That way, reports will only be shown once
    on systems which have /var/crash mounted noatime, too. (LP: #85809)
  * apport/fileutils.py, mark_report_seen(): If os.utime() fails, and opening
    the report file for reading does not change the atime (happens with
    noatime mount option), don't throw an exception, just delete the report.
    (other aspect of LP: #85809)
  * qt4/apport-qt: Wrap gettext() into an unicode(str, 'UTF-8') call,
    otherwise all non-ASCII unicode strings are broken. (LP: #87757)

 -- Martin Pitt <email address hidden> Mon, 26 Feb 2007 20:55:40 +0100

Changed in apport:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.