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] Use search path for scripts


Daniel Jacobowitz wrote:
... what?

It's the source search path because that's what it's used for.  It's
also documented that way:

`-directory DIRECTORY'
`-d DIRECTORY'
     Add DIRECTORY to the path to search for source files.

My patch includes a modification to this documentation to reflect it's update purpose.


Most users don't ever have to add a source path.  If you're using a
modern compiler, and debugging something built locally, and not using
certain kinds of include path constructs (which is unambiguously an
open, and recently discussed, bug in GDB) then GDB will Just Find
Things.

That hasn't changed. The compiler can't tell the debugger where to find its script files though.


I don't find it intuitive that the same path should be overloaded this
way, and it makes changing the source searching algorithm even more
complicated.  However, I'd like to know if any other GDB maintainers
have an opinion on this before I ask you to modify the patch.

I'm not sure a users find it intuitive when they tell a tool to search a directory and then it ignores that directory because there was another way to tell the tool to search that directory, IYSWIM.


I see your point about changing the search algorithm though. Although even then, it might be more intuitive to always use the same algorithm for both. Is it likely to change?

Whatever though, as long as I get a way to search for script files I'm not that fussed.

Andrew


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