Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: [commit] [patch 1/2] auto-load safe-path: Permit shell wildcards
Date: Mon, 02 Jul 2012 10:58:00 -0000	[thread overview]
Message-ID: <20120702105803.GA4220@host2.jankratochvil.net> (raw)
In-Reply-To: <20120622144110.GA32453@host2.jankratochvil.net>

On Fri, 22 Jun 2012 16:41:10 +0200, Jan Kratochvil wrote:
> gdb/
> 2012-06-20  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	Support shell wildcards for 'set auto-load safe-path'.
> 	* auto-load.c: Include fnmatch.h.
> 	(filename_is_in_dir): Rename to ...
> 	(filename_is_in_pattern_1, filename_is_in_pattern): ... here and split
> 	it.  Update function comment.  Rename dir_len to pattern_len.  New
> 	variables filename_len, pattern and filename.  Add more DEBUG_AUTO_LOAD
> 	messages.  Use gdb_filename_fnmatch.
> 	(filename_is_in_auto_load_safe_path_vec): Rename variable dir to
> 	pattern.
> 	(_initialize_auto_load): Extend the "set auto-load safe-path" help text.
> 	* defs.h (gdb_filename_fnmatch): New declaration.
> 	* utils.c: Include fnmatch.h.
> 	(gdb_filename_fnmatch): New function.
> 
> gdb/doc/
> 2012-06-20  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* gdb.texinfo (Auto-loading safe path): Note the shell wildcard
> 	possibility.

Checked in:
	http://sourceware.org/ml/gdb-cvs/2012-07/msg00007.html


Thanks,
Jan


      reply	other threads:[~2012-07-02 10:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 19:37 Jan Kratochvil
2012-06-18 16:09 ` Eli Zaretskii
2012-06-20 18:41   ` Jan Kratochvil
2012-06-20 19:36     ` Eli Zaretskii
2012-06-22 14:41       ` Jan Kratochvil
2012-07-02 10:58         ` Jan Kratochvil [this message]

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=20120702105803.GA4220@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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