This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] -nx-except-gdbtkinit option


Eli Zaretskii wrote:
  gdb -nx-except-gdbtkinit -d scriptdir -x globalscript \
        -x ~/.gdbinit -x ./.gdbinit .....

The purpose is (among other things) to set up transparently (to the user) a selection of user-defined commands (for connecting and configuring target boards) which are available to users in the .gdbinit files.


Sorry, I'm still confused.  Doesn't GDB normally read ~/.gdbinit and
./.gdbinit?  If so, why do you need to use -nx and then load these
init files manually?

I want the .gdbinit files loaded after the mystical 'globalscript' file. Then they can use commands defined by that script.


If -nx is used it has undesirable side effects when using Insight.

In case it wasn't clear, it's those ``undesirable side effects'' are what I was asking to describe in some detail. I don't understand what kind of problems it causes. Perhaps those are misfeatures or bugs we need to fix, instead of introducing a new option.

Without this file Insight does not remember any of your settings, such as window size and position, target settings and breakpoints.


`.gdbtkinit' is a file name, so it should have the @file markup, not
@code.

Other than that, the documentation patch is approved, conditioned on
the code patch approval.  Thanks.

Thanks


Andrew


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]