Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Muhammad Bilal <mbilal@codesourcery.com>
To: <gdb-patches@sourceware.org>
Cc: <pedro_alves@redhat.com>
Subject: Re: [PATCH PR gdb/15715] 'set history filename' to by immediately converted to absolute path.
Date: Fri, 26 Jul 2013 05:13:00 -0000	[thread overview]
Message-ID: <51F20553.4000407@codesourcery.com> (raw)
In-Reply-To: <51E9134D.8070400@codesourcery.com>

On 07/19/2013 03:22 PM, Muhammad Bilal wrote:
> On 07/12/2013 04:05 PM, Bilal, Muhammad wrote:
>> Hi,
>>
>> Please find attached updated patch with new PR in gdb bugzilla.
>> A workaround for this patch has been discussed here,
>> http://sourceware.org/ml/gdb-patches/2013-05/msg00852.html
>>
>>
>>
>>
>>
>> gdb/ChangeLog
>> 2013-07-13  Muhammad Bilal  <mbilal@codesorcery.com>
>>
>>      PR gdb/15715
>>      * top.c (set_history_filename): New function.
>>      Converted history filename path to its absolute path.
>>
>> gdb/testsuite/ChangeLog
>> 2013-07-13  Muhammad Bilal  <mbilal@codesourcery.com>
>>
>>      PR gdb/15715
>>      * gdb.base/setshow.exp: Test 'set history filename' command
>>      to check its absolute path.
>>
>>
>>
>> Thanks,
>>
>> -Bilal
>>
>>
>>
>>
>>
>>
>>
> ping
>
> Thanks
> -Bilal
ping?


  reply	other threads:[~2013-07-26  5:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <97B73E257CC18646B0B5D3DD77DCBDD15DA063@EU-MBX-02.mgc.mentorg.com>
2013-07-12 11:05 ` Bilal, Muhammad
2013-07-19 10:22   ` Muhammad Bilal
2013-07-26  5:13     ` Muhammad Bilal [this message]
2013-07-26 12:49   ` Pedro Alves
2013-07-29  6:12     ` Muhammad Bilal
2013-07-29 14:43       ` Pedro Alves
2013-07-30  9:56         ` Muhammad Bilal
2013-07-30 10:09           ` Pedro Alves
2013-07-30 10:47             ` Muhammad Bilal
2013-07-30 11:33               ` Pedro Alves
2013-07-30 12:11                 ` Muhammad Bilal

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=51F20553.4000407@codesourcery.com \
    --to=mbilal@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro_alves@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