public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "asutherland at asutherland dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/12121] Apparent non-determinism in DWARF symbol resolution
Date: Thu, 14 Oct 2010 03:48:00 -0000	[thread overview]
Message-ID: <20101014034800._GskdyzR8f_ZbwEMyrOIiLhbDLpg0IEEaSU9oK-6cf4@z> (raw)
In-Reply-To: <bug-12121-1110@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12121

--- Comment #2 from Andrew Sutherland <asutherland at asutherland dot org> 2010-10-14 03:48:23 UTC ---
Oh, and if you would like to reproduce using your own build, Thunderbird build
instructions can be found here:
https://developer.mozilla.org/en/Simple_Thunderbird_build

I am building with the following .mozconfig file in use:
ac_add_options --enable-application=mail

ac_add_options --enable-debug
ac_add_options --enable-debugger-info-modules=yes
ac_add_options --enable-extensions=default,inspector
ac_add_options --disable-optimize

ac_add_options --enable-chrome-format=symlink

# BAD BAD BAD, but I don't like crashes :(
ac_add_options --disable-accessibility

mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-thunderbird-debug
mk_add_options MOZ_MAKE_FLAGS="-s -j6"


If you want to recreate the full experience:
hg clone http://hg.mozilla.org/users/bugmail_asutherland.org/tb-test-help/

The log file I previously attached already tells you what the actual stap run
arguments were.  Unfortunately at least the -x part is somewhat hard to create
because my wrapper script does its own variation on '-c' by forking a thread. 
(I think staprun was destroying my environment so xpcshell failed to run and
that was my workaround... although I think there were other pipe benefits to
that strategy.)

Once a build completes, I...
a) change to an output directory where I can run my unit test
cd obj-thunderbird-debug/mail/base/test

b) run my unit test with my test framework thing:
make SOLO_FILE=test_viewWrapper_virtualFolder.js EXTRA_TEST_ARGS="--debugger
/home/visbrero/rev_control/hg/tb-test-help/systemtap/chewchewwoowoo.py
--debugger-args
'/home/visbrero/rev_control/hg/tb-test-help/systemtap/mozperfish/mozperfish.stp
--'" check-one

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-10-14  3:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14  3:37 [Bug translator/12121] New: " asutherland at asutherland dot org
2010-10-14  3:39 ` [Bug translator/12121] " asutherland at asutherland dot org
2010-10-14  3:48 ` asutherland at asutherland dot org [this message]
2010-10-14  3:53 ` asutherland at asutherland dot org
2010-10-14 12:13 ` fche at redhat dot com
2010-10-14 12:22 ` asutherland at asutherland dot org
2010-10-14 12:23 ` asutherland at asutherland dot org
2010-10-14 12:24 ` asutherland at asutherland dot org
2010-10-14 12:25 ` asutherland at asutherland dot org
2010-10-14 18:13 ` jistone at redhat dot com
2010-10-14 18:49 ` jistone at redhat dot com
2010-10-14 18:51 ` jistone at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101014034800._GskdyzR8f_ZbwEMyrOIiLhbDLpg0IEEaSU9oK-6cf4@z \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).