Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr>
To: gdb-patches@sources.redhat.com
Subject: Re: handling of absolute source file paths
Date: Wed, 21 Apr 2004 11:10:00 -0000	[thread overview]
Message-ID: <20040421111027.GA15823@ata.cs.hacettepe.edu.tr> (raw)
In-Reply-To: <ud661962c.fsf@elta.co.il>

Hello, Eli!

This was FAST 8) , thank you!

On Wed, Apr 21, 2004 at 08:51:55AM +0200, Eli Zaretskii wrote:
>   Each time GDB wants a source file, it tries all the directories in
>   the list, in the order they are present in the list, until it finds
>   a file with the desired name
> 
> Note that it doesn't specify what happens if the file's name starts
> with a slash or otherwise has leading directories.  It would be good
> to augment the manual with a more explicit description of cases such
> as yours.  Would you like to do that?

I will try. Actually, I think my case is covered, but more on it
certainly wouldn't hurt. I'm going to give some examples that I've
played with during testing. Another question is whether such kind of
detail is suitable for "Debugging with GDB", which I'd like to see as a
possibly shortest introduction; but I suppose we don't want to start
"GDB reference manual" now ;) .


> First, please in the future send patches as plain text, not as
> compressed binary attachments; that might help your patches to be
> reviewed sooner.

I will. The reason is highly motivating :) . I usually send them
compressed after an incident with a buggy MTA that reformatted my
patch.


> I don't know if you need an assignment for this patch, so I'll let
> others to give you a definitive answer.

Ok. Basically, it's a less-than-15-liner with repeating series, as
described in http://www.gnu.org/prep/maintain_6.html#SEC6 .


Waiting for an answer on both subjects...


With kind regards,
Baurjan.


  reply	other threads:[~2004-04-21 11:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20 15:49 Baurjan Ismagulov
2004-04-21  5:51 ` Eli Zaretskii
2004-04-21 11:10   ` Baurjan Ismagulov [this message]
2004-05-01 17:01   ` Baurjan Ismagulov
2004-05-02 13:15     ` Eli Zaretskii
2004-05-01 17:12   ` Baurjan Ismagulov
2004-05-01 18:11     ` Eli Zaretskii
2004-05-08 21:20       ` Baurjan Ismagulov
2004-05-09 14:33         ` Eli Zaretskii
2004-05-09 13:53           ` Baurjan Ismagulov
2004-05-11 16:08         ` Eli Zaretskii
2004-07-17 18:20           ` Baurjan Ismagulov
2004-07-23 19:55             ` ping: " Baurjan Ismagulov
2004-07-24  7:21               ` Eli Zaretskii
2004-07-26 14:57                 ` Andrew Cagney
2004-07-26 15:20                   ` Baurjan Ismagulov
2004-07-26 17:48                     ` Eli Zaretskii
2004-07-26 18:15                     ` Andrew Cagney
2004-07-26 17:47                   ` Eli Zaretskii
2004-07-30 19:19             ` Eli Zaretskii
2004-07-31  7:57               ` Baurjan Ismagulov
2004-07-31  8:25                 ` Eli Zaretskii
2004-08-01 19:31                   ` Andrew Cagney
2004-08-03 16:59                     ` Baurjan Ismagulov
2004-08-03 19:12                       ` Eli Zaretskii
2004-08-04  7:02                         ` Baurjan Ismagulov

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=20040421111027.GA15823@ata.cs.hacettepe.edu.tr \
    --to=ibr@ata.cs.hun.edu.tr \
    --cc=gdb-patches@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