Retraces

[David Farning]

On 2/22/07, John Vivirito <gnomefreak at gmail.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi everyone,
> Here is a bit of a tut on using apport to retrace bugs. PLEASE USE
> FEISTYS APPORT IN EDGY'S CHROOT.
>
> Edgy: 1) you need to look at _usr_lig_firefox.... crash report to see
> what version of firefox they are using. its either gonna be
> 2.0+0dfsg-0ubuntu3 or version 2.0.0.1+0dfsg-0ubuntu0.6.10 anything other
> than that you need to ask for a newer crash report.
>
> 2) install the firefox and firefox-dbg for what ever version the crash
> report used. to install the older version the command is: "sudo apt-get
> install firefox=2.0+0dfsg-0ubuntu3 firefox-dbg=2.0+0dfsg-0ubuntu3" ok i
> also installed every package i could including ubuntu-desktop package in
> my edgy chroot. and any other related -dbg package. When you do the
> retrace it will tell you what versions it needs adn if its gonna use a
> different version. i also have flash7 and sun-java5-plugin installed.
>
> 3) Here is the steps i take to do a retrace for edgy after everything is
> set up.
> A. in home dir. i mkdir bug8888 than i cd bug8888 and i mkdir <each
> reporter with a crash uploaded> and in each reporter folders i mkdir
> parts (rest of examples will be assuming there is only one reporter.
> B. cd bug8888 (if using chroot make sure your in it.)
> C. Click on crash report and make sure its got a coredump and what
> version it was using
> D. wget <address to crashreport when you clicked on it> example to follow.
> (mychroot)gnomefreak at FeistyFawn:~/bug48772/theo$ wget
>
> http://librarian.launchpad.net/5970656/_usr_lib_firefox_firefox-bin.1000.crash
> E. when its done downloading run apport-retrace.example to follow:
>
> (mychroot)gnomefreak at FeistyFawn:~/bug48772/gquigs$ apport-retrace -o
> retrace.crash -v -d _usr_lib_firefox_firefox-bin.1000.crash 2>&1 | tee
> retrace.log
>
> That comand will not touch the orignal crash report you downloaded. the
> crash report with symbols will be retrace.crash and the log of
> warnings... will be in retrace.log.   the -o==dont touch orignal crash
> report. -v== verbose -d=download -dbgsym packages needed,
>
> F. cat retrace.crash | less (to make sure the report came out ok)
> G. if all is good. run: "apport-unpack retrace.crash parts" that will
> unpack the crash report in to the parts folder. unpacking is seperating
> crash report into chunks (you might get an "assertion error" Ignore that
> for now since it hasnt yet been fixed. I will be trying the newest
> apport in feisty in edgys chroot. Than upload the stacktrace and
> threadstacktrace if you have a threadstacktrace.
>
>
> Feisty.
> Feisty's crash reports that are unpacked on bug report. it will list 4or
> so reports in one comment. coredump, stacktrace dissasembly.....
>
> these are not too hard just take time.No need to download report. i
> still make the dir. as in edgy example mkdir bug8888 cd bug8888 DONT DO
> MORE THAN ONE AT A TIME PER REPORT.
>
> Ok now everything set up your in the bug8888 dir.
> command: apport-retrace -s -d 8888 2>&1 | tee retrace.log
>
> replace 8888 with the number of the bug report your working on. and than
> just upload the retrace.log file and you should be ok.
>
> NOTE: for all of the crash reports you do you will want as many -dbg
> packages as you can get due to the lack of -dbgsym packages that have
> been updated.
>
> If you have any questions please ping me on IRC or email me i will get
> back to you ASAP faster if you ping me on IRC.
>
> If someone feels this info is needed as a wiki (I do) can you please
> outline one with this info and i will see if i can make any changes. I
> SUCK AT WIKIS BADLY (check mine if you dont believe me :)
>
> - --

 Thanks for the mini tutorial I"ll try to turn it into a mini wiki and also
forward it the the apport team.


thanks
david
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-mozillateam/attachments/20070222/128aa7fa/attachment-0001.htm