This is the mail archive of the gdb@sources.redhat.com 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: probing GDB for MI versions


gcc has many options with similar purposes:

  -print-file-name=LIBRARY
    Print the full absolute name of the library file LIBRARY
    that would be used when linking--and don't do anything else.
    With this option, GCC does not compile or link anything;
    it just prints the file name.

  -print-multi-directory
    Print the directory name corresponding to the multilib selected
    by any other switches present in the command line.   [et cetera]

  -print-multi-lib
    Print the mapping from multilib directory names to compiler
    switches that enable them.  [et cetera]

  -print-prog-name=PROGRAM
    Like -print-file-name, but searches for a program such as cpp.

  -print-libgcc-file-name
    [et cetera]

  -print-search-dirs
    [et cetera]

  -dumpmachine
  -dumpversion
  -dumpspecs
    [et cetera]

This situation looks very similar.  So if -print-XXX and --dumpYYY
are working well for gcc, then "gdb -print-mi-versions" ought to
be fine.  Like Bob, I don't have a problem with invoking gdb twice.

Just my two cents,

Michael


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