From: Sami Wagiaalla <swagiaal@redhat.com>
To: Ray Ruvinskiy <rruvinsk@sybase.com>
Cc: frysk@sourceware.org
Subject: Re: Specifying a debuginfo path independently of sysroot
Date: Fri, 13 Jun 2008 15:07:00 -0000 [thread overview]
Message-ID: <4852804D.30601@redhat.com> (raw)
In-Reply-To: <962B19CF-9923-42EC-9732-BFE1AB7E07DB@sybase.com>
Hi Ray,
> I was wondering if it was possible to pass a custom debuginfo path from
> frysk to libdwfl without using the -sysroot switch.
I guess the first question is why would one want to do this ?..maybe
there is a larger problem that we should fix, also for the record :)
> If this is not currently possible, I was wondering if it might be
> desirable to allow for this. I wouldn't mind taking a crack at
> implementing this, if given an idea as to what semantics would be desired.
If you do go for it here are a couple of things to look out for:
1) I think CommandLineParser.java would be a good spot to add it so that
the functionality tricles down to all the command line utilities.
2) We are currently in a slow switch from CNI to JNI so we have two sets
of bindings that we are maintaining. So if you do touch the bindings
make sure you update the JNI side of things... hopefully this would be
over by frysk 0.5 :)
3) It would be really cool if your patch comes with a test case. The
frysk test suite is nice to work with now-a-days. You can find examples
in Test*.java... then copy/paste and edit.
Cheers,
Sami
next prev parent reply other threads:[~2008-06-13 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 14:12 Ray Ruvinskiy
2008-06-13 15:07 ` Sami Wagiaalla [this message]
2008-06-13 15:56 ` Ray Ruvinskiy
2008-06-13 21:14 ` Rick Moseley
2008-06-16 12:22 ` Ray Ruvinskiy
2008-06-16 13:20 ` Stan Cox
2008-06-18 13:27 ` Rick Moseley
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=4852804D.30601@redhat.com \
--to=swagiaal@redhat.com \
--cc=frysk@sourceware.org \
--cc=rruvinsk@sybase.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).