I don't understand what is going on.
I tried applying patches upto 23 as one block then applying patches
24,25,26,27,28 and 29 in one at a time, running ./configure between each
and could not reproduce the problem.
Yet if I pull bash43 source in and apply all 29 patches and
then ./configure I
dmesg.
[307688.764489] configure[25847]: segfault at 9558104 ip 080e2246 sp bfd478f0
error 4 in bash[8048000+148000]
[307689.436739] configure[25966]: segfault at 95580b4 ip 080e2246 sp bfd478f0
error 4 in bash[8048000+148000]
[307689.467279] configure[25983]: segfault at 9558104 ip 080e2246
On Thu, 2014-10-09 at 19:56 -0400, Chet Ramey wrote:
> On 10/8/14, 8:17 PM, jon wrote:
> > dmesg.
> >
> > [307688.764489] configure[25847]: segfault at 9558104 ip 080e2246 sp
> > bfd478f0 error 4 in bash[8048000+148000]
> > [307689.436739] configure[25966]: s
On Fri, 2014-10-31 at 15:56 -0700, Eduardo A. Bustamante López wrote:
> > well, help time clearly states how it should be used.
> You are clearly not understanding the point.
>
> The point is: why does
>
> time
>
> work, but
>
> time ; somecommand
>
> doesn't.
>
> It's that simple. It's
> | When the shell is in posix mode, time may be followed by a newline. In
> this case, the shell displays the
> | total user and system time consumed by the shell and its children. The
> TIMEFORMAT variable may be used
> | to specify the format of the time information.
>
Two comments.
1)
>But, the thing is... it shouldn't be a syntax error, right?
I agree, this thread is really about 2 issues. The interpreter barf
with "time;" and the fact that "time " is broken - I suspect
the two issues are not related.
> According to my tests, it also fails like OP reported in posix mode:
The
You do realise that if you allow an untrusted script to run at root, having
it modify itself is the least of your concerns. There are *so* many ways an
untrusted script can cause a problem that do not require your
self-modifying script and for which your proposed mitigation will do
nothing. What's
xpect it to work on OSX (3.2.17) since
.bash_history doesn't seem to have a format that would allow it. The
version I tried on Linux 3.2.25 does have a .bash_history format that
could support it, but it still behaved the same way.
jon.
> Bob
>
>
In the version I was using a line that began with # and perhaps a timestamp
separated each entry of the history in a way that in principle preserved
information about the entry boundary even though this information is not used
by bash on the subsequent start.
jon.
On 06/02/2011, at 11:24
Here's the format I see in my history.
#1296950184
for i in 1 2
do
echo $i
done
#1296950194
exit
HISTTIMEFORMAT is:
HISTTIMEFORMAT='[%m.%d.%y] %T '
bash -version is:
GNU bash, version 3.2.25(1)-release (i686-redhat-linux-gnu)
Copyright (C) 2005 Free Software Foundation, Inc.
On Sun, Feb 6, 2011 at 1:02 PM, Michael Witten wrote:
> On Sat, Feb 5, 2011 at 19:15, Jon Seymour wrote:
>
> So, if you run `history', you'll not only get the commands in the
> history list, but you'll also get the time at which the commands
> were la
e one
entry,
#1296950290
pwd
#1296950293
bash -version
#1296950327
for i in 1 2
do
echo $i
done
#1296950337
jon.
Good catch - how long did that take to find?
jon.
On Thu, Feb 10, 2011 at 6:06 AM, Eric Blake wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash'
27;cd /tmp; pwd'
/home/jseymour
My expectation is that the last command should print:
/tmp
But, instead, the cd command seems to be completely ignored when bash
is run under ssh. I have reproduced this with bash 4.1.5 on Linux and
bash 3.0.0 on AIX.
jon.
Correction - a _leading_ cd command and only a leading cd command,
seems to be completely ignored in the case I described.
Why is this?
jon.
-- Forwarded message --
From: Jon Seymour
Date: Sat, Feb 12, 2011 at 2:18 PM
Subject: Can someone explain this?
To: bug-bash@gnu.org
x27;
and then pwd is invoked, presumably in same shell that invoked bash.
This can be seen with this:
jseymour@ubuntu:~$ ssh localhost bash -c 'echo\ \$\$\ \$PPID' ';' echo '$$'
11553 11552
11552
bash is invoked with:
'-c'
'echo $$ $PPID'
then:
ech
nd line. Quoting is then much simplified.
>
Makes sense...thanks.
jon.
Has anyone ever come across an equivalent to Linux's readlink -f that
is implemented purely in bash?
(I need readlink's function on AIX where it doesn't seem to be available).
jon.
On Tue, Aug 9, 2011 at 12:49 PM, Bob Proulx wrote:
> Jon Seymour wrote:
>> Has anyone ever come across an equivalent to Linux's readlink -f that
>> is implemented purely in bash?
>>
>> (I need readlink's function on AIX where it doesn't seem to be ava
On Tue, Aug 9, 2011 at 1:36 PM, Bob Proulx wrote:
> Jon Seymour wrote:
>> readlink -f will fully resolve links in the path itself (rather than
>> link at the end of the path), which was the behaviour I needed.
>
> Ah, yes, well, as you could tell that was just a partial solut
On Tue, Aug 9, 2011 at 2:14 PM, Bob Proulx wrote:
> Jon Seymour wrote:
>> I always use sed for this purpose, so:
>>
>> $(cd "$dir"; ls -l "$base" | sed "s/.*->//")
>>
>> But, with pathological linking structures, this isn
On Tue, Aug 9, 2011 at 2:36 PM, Jon Seymour wrote:
> On Tue, Aug 9, 2011 at 2:14 PM, Bob Proulx wrote:
>> Jon Seymour wrote:
>>> I always use sed for this purpose, so:
>>>
>>> $(cd "$dir"; ls -l "$base" | sed "s/.*->//"
On Tue, Aug 9, 2011 at 2:51 PM, Bob Proulx wrote:
> Jon Seymour wrote:
>> readlink_f()
>> {
>> local path="$1"
>> test -z "$path" && echo "usage: readlink_f path" 1>&2 && exit 1;
>
> An extra
On Tue, Aug 9, 2011 at 7:29 PM, Bernd Eggink wrote:
> On 09.08.2011 03:44, Jon Seymour wrote:
>>
>> Has anyone ever come across an equivalent to Linux's readlink -f that
>> is implemented purely in bash?
>
> You can find my version here:
>
> http://sud
On Mon, Aug 8, 2011 at 8:42 AM, Bob Proulx wrote:
>
> People sometimes read the POSIX standard today and think it is a
> design document. Let me correct that misunderstanding. It is not.
> POSIX is an operating system non-proliferation treaty.
Love it!
jon.
/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
jon.
On 27/05/2012, at 17:39, Geir Hauge wrote:
> 2012/5/27 Jon Seymour :
>> Is there a reason why bash doesn't treat == as an illegal test
>> operator when running in POSIX mode?
>
> POSIX does not say == is not allowed.
>
> POSIX tells you what the shell should
On Sun, May 27, 2012 at 9:24 PM, Dan Douglas wrote:
> On Sunday, May 27, 2012 08:45:46 PM Jon Seymour wrote:
>> On 27/05/2012, at 17:39, Geir Hauge wrote:
>>
>> I guess the question is better phrased thus: what use case is usefully
> served by having bash's POSIX mo
On Sun, May 27, 2012 at 9:31 PM, Andreas Schwab wrote:
> Jon Seymour writes:
>
>> As it stands, I can't use bash's POSIX mode to verify the validity or
>> otherwise of a POSIX script because bash won't report these kinds of
>> errors - even when runni
On Sun, May 27, 2012 at 11:09 PM, Jon Seymour wrote:
> On Sun, May 27, 2012 at 9:31 PM, Andreas Schwab wrote:
>> Jon Seymour
> ** I guess I can except that current bash behaviour is, on balance,
except -> accept
res available.
> Most people shouldn't have to worry about avoiding it.
>
Thanks, I'll have a read.
jon.
On Tue, May 29, 2012 at 1:08 AM, Eric Blake wrote:
> On 05/27/2012 07:09 AM, Jon Seymour wrote:
>
>> I understand that the behaviour is unspecitied by POSIX - I didn't
>> know that before, but I know that now - thanks.
>>
>> That said, from the point of view
ne'
+ false
So... bug or feature? Thanks in advance for the help.
- Jon
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
On Mon, 2005-09-26 at 21:39 -0600, Bob Proulx wrote:
> Jon Salz wrote:
> > I'm noticing a difference in behavior between Solaris 9's sh and GNU
> > bash, and was wondering if this is a bug or a feature.
>
> I believe Solaris' sh is the Bourne shell. I am
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: cygwin
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i686-pc-cygwin'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA\
GE='bash' -
Apologies, I see that is true.
jon.
On Fri, Aug 15, 2008 at 3:36 PM, Pierre Gaston <[EMAIL PROTECTED]> wrote:
> It's listed in the BUGS section of my man page (last line of the page):
> "Array variables may not (yet) be exported."
>
effort re-inventing the
wheel, I'd be interested in learning of other efforts in this area.
jon seymour.
hen guard the call to the those
functions with enclosing subshells as required - that's a choice you make in
bool_foo.
I agree a formal exception mechanism would be nice, but I have found that
use of exit and the subshell feature does allow most exception handling
patterns to be emulated reasonably well.
jon seymour.
re any way I can have an ssh pseudo-tty and get bash to execute
~/.bashrc?
jon seymour.
Chet,
Thanks for that info.
Due to the circumstances, recompiling bash isn't really an option for me, so
I decided to deal with it by having ssh invoke a script that could guarantee
~/.bashrc was sourced.
Regards,
jon seymour.
On Wed, Oct 15, 2008 at 1:24 PM, Chet Ramey <[EMAIL P
/bin/ssh-target.sh cmd args...
At the cost of having to have /usr/local/bin/ssh-target.sh (or
equivalent) available everywhere, you can at least avoid dependencies
on particular combinations of ssh and bash.
jon.
On Thu, Oct 23, 2008 at 9:52 PM, Roman Rakus <[EMAIL PROTECTED]> wrote:
> R
; aaa ; )
aaa
which is what you observed.
Use unalias aaa and then you will get:
$ alias aaa='echo aaa'; ( alias aaa='echo bbb'; aaa ; )
-bash: aaa: command not found
jon.
On 11/01/2009, at 23:18, Коренберг Марк
wrote:
> Configuration Information [Automatica
Not sure this is correct. The ] is parsed by the shell but only if it
surrounded by whitespace. This is why the -n option reports an error,
since -n suppresses command execution.
I suspect the behaviour is required by posix or at least historical
precedent.
jon.
On 12/02/2009, at 7:04
On Thu, Feb 12, 2009 at 8:02 AM, Paul Jarc wrote:
> Jon Seymour wrote:
>> Not sure this is correct. The ] is parsed by the shell
>
> It's parsed by the [ command. That happens to be a builtin command,
> so yes, it is done by the shell, but it is not part of the grammar
There may be other ways to do this, but:
CPATH="${CPATH}${CPATH:+:}$(echo ~usr1/blah/blah)"
should work.
jon.
On Mon, Feb 16, 2009 at 9:02 AM, Angel Tsankov wrote:
> Chet Ramey wrote:
>> Angel Tsankov wrote:
>>> Hi,
>>>
>>> Using bash
On Mon, Feb 16, 2009 at 9:26 AM, Angel Tsankov wrote:
> Jon Seymour wrote:
>> There may be other ways to do this, but:
>>
>> CPATH="${CPATH}${CPATH:+:}$(echo ~usr1/blah/blah)"
>>
>> should work.
>
> Well, I'd like to avoid the use of
reconsider, since command substitution is one of
bash's most powerful features.
[ Of course, others more experienced with bash idioms may object to
$(echo ~usr1/blah/blah) on aesthetic grounds too - I welcome any
suggested improvement!. ]
jon.
On Mon, Feb 16, 2009 at 9:54 AM, Angel Tsankov wrote:
On Mon, Feb 16, 2009 at 10:22 AM, Paul Jarc wrote:
> Jon Seymour wrote:
>> If the builtin echo fails it will be because the bash interpreter has
>> suffered a catastrophic failure of some kind [ e.g. run out of memory
>> ]. Once that has happened, all bets are off anyway.
&
On Mon, Feb 16, 2009 at 11:44 AM, Paul Jarc wrote:
> Jon Seymour wrote:
>> On Mon, Feb 16, 2009 at 10:22 AM, Paul Jarc wrote:
>>> CPATH=${CPATH:+$CPATH:}${#+~usr1/blah/blah}
>>
>> Out of interest, how does one derive that outcome from the documented
>&g
d too.
$@ wouldn't work if the positional parameters in the current context
happened to be empty as is easily demonstrated.
echo $...@+~jon} -> empty
echo ${?+~jon} -> /home/jon
echo ${#+~jon} -> /home/jon
jon.
On Mon, Feb 16, 2009 at 11:49 AM, Angel Tsankov
wrote:
> Paul Jarc wrote:
On Mon, Feb 16, 2009 at 12:11 PM, Paul Jarc wrote:
> Jon Seymour wrote:
>> The manual specifies a rule for ${parameter:+word}, but not
>> ${parameter+word}.
>
> It's there, but easy to miss:
> In each of the cases below, word is subject to tilde expansion, p
han to have them silently co-erced to the corresponding
unsigned integers . The bash 3.0 behaviour played havoc with a binary
search algorithm that I wrote until I realised that -1 had been
coerced to 255.
jon.
ot;$cmd"
Then:
as-echo.sh 'a' '$(foobar)' 'c'
would produce:
echo 'a' '$b' 'c'
a $b c
Is my code safe, or can someone maliciously choose arguments to
as-echo.sh that could cause it (as-echo.sh) to do something other than
write to stdout?
Can anyone point me to best practice for this kind of protection in bash?
jon.
Yes, I realised that I should have at least used // after I posted,
not that that would have been sufficient. Thanks for the solution.
jon.
On Mon, May 11, 2009 at 10:20 PM, Greg Wooledge wrote:
> On Mon, May 11, 2009 at 10:35:18AM +1000, Jon Seymour wrote:
>> I am trying to parse
There are at least 3 things wrong with your snippet.
Try:
IPS=(( 89.17.206.180 89.17.206.185 89.17.206.186 89.17.206.187 ))
for k in ${i...@]}
do
nmap -p 22 $k
done
jon.
On 07/07/2009, at 4:55 AM, tirengarfio wrote:
IPS={89.17.206.180,89.17.206.185,89.17.206.186,89.17.206.187}
on cygwin.
I'd be interested to know if there are any good solutions to this
problem already in existence.
jon.
Oh, cool. Thanks for correcting me!
jon.
On Sat, Dec 5, 2009 at 11:54 AM, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Jon Seymour on 12/4/2009 4:00 PM:
>> On Linux or any reasonable OS, I could do this remote dispatch easily
>&g
resulting script will work with all bash
instances irrespective of what the argument limit on the particular bash
instance you are presented with is.
jon.
On Tue, Jan 26, 2010 at 11:03 AM, Peng Yu wrote:
> I got the following message. Is there a way to configure bash such
> that there is
trivial means to suppress such commands from their command history?
Or, is it motivated by some other use case where suppressing commands
with a leading space is useful? What is that use case?
Regards,
jon.
to encode such a list so
that the resulting variable is readily compose-able and decodeable? In
particular, I'd like to avoid the use of (unescaped) separators which
might themselves be used in the filename.
jon.
| question -> _forum_
On 8/29/10, Jon Seymour wrote:
> This isn't strictly a bash question, and I'd prefer a POSIX-only
> solution if possible [ suggestions as to a good _forum_ to ask
> POSIX-only questions would be appreciated ].
>
> Suppose I need to encode a lis
GIT_EXTRA_CONDITION_LIBS="libA.sh 'lib B.sh' libC.sh"
I am lucky in that I can assume the existence of git rev-parse on my
path and I am prepared to write the decoding glue in my script.
Anyway, thank you all for your input.
jon.
On Mon, Aug 30, 2010 at 11:07 PM, Gre
On Mon, Aug 30, 2010 at 11:33 PM, Greg Wooledge wrote:
> On Mon, Aug 30, 2010 at 11:25:00PM +1000, Jon Seymour wrote:
>> I am working on an extension to git, and need to store a list of shell
>> files that can be used to extend the capabilities of the command I am
>> writing
bash
set -e
set -o pipefail
set -o procsubfail
cat <(echo hi; exit 1)
echo 'This doesn't print now and code isn't messy'
Thanks for the wonderful shell,
Jon
jhcl...@cs.cmu.edu
http://www.cs.cmu.edu/~jhclark
PhD Student
School of Computer Science
Carnegie-Mellon University
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
at sh can parse and allows exported functions to
>> be used in the environment that calls at.
>>
> ...
>
> Jon Seymour asked me if my at patch would fix the following vulnerablity
> (presumably in at(1))
>
> echo pwd | env "/tmp/exploit=me" at tomorr
| correction: variable called "/tmp/exploit=me" => a variable called
"/tmp/exploit" with a value "me"
On Mon, Sep 29, 2014 at 2:26 AM, Jon Seymour wrote:
> To clarify, I am not sure that the presence of a variable called
> "/tmp/exploit=me"
s" in yes) echo yes; ;; no)
echo no; ;; esac)'
It does work with bash 4.x.
Is this a known issue with 3.2 or is it particular to the OSX
implementation (which in my case is 3.2.53(1))?
jon.
Thanks for reply and the workaround.
jon.
On Sun, Mar 22, 2015 at 4:49 PM, Chris F.A. Johnson
wrote:
> On Sun, 22 Mar 2015, Jon Seymour wrote:
>
>> I was surprised that this didn't work with the OSX version of bash 3.2:
>>
>> /bin/bash -c 'echo $(case &quo
Hi,
Just tried to submit a bug, but bashbug command failed, so here is the problem
text.
Thanks,
Jon
From: jonmorris
To: bug-bash@gnu.org
Subject: cygheap base mismatch detected
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: msys
Compiler: gcc
No problem. I don't have cygwin installed so the problem is something is
looking for it. I've reinstalled git for windows so if the problem doesn't go
away, I'll raise a defect with Cmder.
Thanks,
Jon
-Original Message-
From: Eduardo Bustamante [mailto:dual...@gmai
You can do
ffmpeg -i intro.mpv output.mpv
and when you cursor over ffmpeg it highlights
and over output.mpv you can do ctrl+enter and it'll list file contents
it should be as easy as
if (cursor = word)
highlight(word)
or
if (text->word = text->highlight)
show(combo_box)
and a customizable pr
72 matches
Mail list logo
