On 2/19/23 9:34 AM, Mr. Dick Steel wrote:
On 19-02-2023 16:21, Martin D Kealey wrote:
at this point, what is in the file? does « wc -l .bash_history » report 13?
It reports:
13 .bash_history
If I disable PS1 coloring, everything works correctly.
You can also mark these sequences of non-
On 19-02-2023 16:21, Martin D Kealey wrote:
at this point, what is in the file? does « wc -l .bash_history »
report 13?
It reports:
13 .bash_history
If I disable PS1 coloring, everything works correctly.
I suspect the history file is corrupt; truncating a file while another
process has it open for writing can do strange things.
On Sun, 19 Feb 2023, 23:05 Mr. Dick Steel, wrote:
> WARNING: The following will REPLACE your
> current .bash_history file! Take care.
>
> 1. Start you term
On 19-02-2023 16:07, Greg Wooledge wrote:
On Sun, Feb 19, 2023 at 03:05:24PM +0200, Mr. Dick Steel wrote:
4. Use up arrow to scroll cmd history up until you hit:
"$ valgrind --leak-check=full
./target/debug/hostname-ip-address"
and press up arrow once more and you will get:
On Sun, Feb 19, 2023 at 03:05:24PM +0200, Mr. Dick Steel wrote:
> 4. Use up arrow to scroll cmd history up until you hit:
> "$ valgrind --leak-check=full ./target/debug/hostname-ip-address"
> and press up arrow once more and you will get:
> "$ valgrind -cd rust/hostname-
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs
