public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Ray Ruvinskiy <rruvinsk@sybase.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: Specifying a debuginfo path independently of sysroot
Date: Fri, 13 Jun 2008 15:56:00 -0000	[thread overview]
Message-ID: <E23A2A83-9C3D-4081-99B0-9795E8BE048F@sybase.com> (raw)
In-Reply-To: <4852804D.30601@redhat.com>

Hi Sami,

We save debug symbols for every build on a central server. The  
binaries that are tested (and shipped) are stripped, except for a  
gnu_debuglink. To debug issues on QA machines or customer issues, we  
find it convenient to simply create a symbolic .debug link from the  
directory where the binaries and libraries are installed to where we  
keep the symbols for the particular build we want to debug. The  
directory structure of the symbol repository does not necessarily  
match the directory structure of the location where the software was  
installed.

Thanks,

Ray

On 13-Jun-08, at 10:12 AM, Sami Wagiaalla wrote:

> 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
>

  reply	other threads:[~2008-06-13 15:07 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
2008-06-13 15:56   ` Ray Ruvinskiy [this message]
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=E23A2A83-9C3D-4081-99B0-9795E8BE048F@sybase.com \
    --to=rruvinsk@sybase.com \
    --cc=frysk@sourceware.org \
    --cc=swagiaal@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).