[Octave-bug-tracker] [bug #53241] .gdbinit macros for Octave debugging no longer work

[Dan Sebald]

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
/home/usr3/octave/octave/octave/etc/gdbinit
libinterp/parse-tree/oct-parse.output is unchanged
refusing to overwrite .gdbinit with newer version from
/home/usr3/octave/octave/octave/etc/gdbinit


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:

https://savannah.gnu.org/bugs/?50285#comment4


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53241>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/