[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53241] .gdbinit macros for Octave debugging n

From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #53241] .gdbinit macros for Octave debugging no longer work
Date: Tue, 27 Feb 2018 20:47:00 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Follow-up Comment #2, bug #53241 (project octave):

Where are you placing the .gdbinit file?  I'm just curious because during
repeated building there is always this message

refusing to overwrite test/.gdbinit with newer version from
libinterp/parse-tree/oct-parse.output is unchanged
refusing to overwrite .gdbinit with newer version from

which isn't an error or warning, it is simply a statement that the .gdbinit
file isn't going to be written into the build directory because of a
pre-existing .gdbinit file.  Is this a natural location for a .gdbinit file to
be, i.e., the build directory test/.gdbinit?  Is there a test procedure that
is performed during build that requires a .gdbinit file to be there?  During
"make install" does that .gdbinit file get placed in some system-wide
location?  Is there a consequence to always overwriting .gdbinit file if
someone has such information typically stored elsewhere?

Links to common locations for .gdbinit files is given here:



Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]