Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: "Daniel Jacobowitz" <drow@mvista.com>, <gdb-patches@sources.redhat.com>
Subject: Re: patch to add QNX NTO i386 support
Date: Thu, 27 Feb 2003 20:28:00 -0000	[thread overview]
Message-ID: <035901c2de9e$c7a93770$0202040a@catdog> (raw)
In-Reply-To: <3E5E7458.3060706@redhat.com>

> > That being said, I'm of the opinion that exec-file should be
unconditional.
> > If symbol-file is set to one thing and exec-file to another, should gdb
even
> > need to check to see if exec-file exists?  I haven't looked to see what
info
> > exec-file seems to feel it needs from the binary but I figure the run
> > command will discover that the exec file isn't there and report an error
> > itself.  Then, in our case, the run command spawns on the remote and
> > everyone is happy and we don't need a special command.
>
> Good point.  Would a doco / code comparison be better to see if what
> currently goes on makes sense?

The docs only say the following:

<doc>

exec-file [ filename ]
Specify that the program to be run (but not the symbol table) is found in
filename. GDB searches the environment variable PATH if necessary to locate
your program. Omitting filename means to discard information on the
executable file.

</doc>

Right now it errors out if it doesn't find the file.  Inquiry: does
searching the path seem like a sensible thing to do?  It seems to me that
there could be unforseen consequences.

Kris


  reply	other threads:[~2003-02-27 20:28 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 20:19 Kris Warkentin
2003-02-04  7:23 ` Eli Zaretskii
2003-02-04 13:33   ` Kris Warkentin
2003-02-04 13:53     ` Kris Warkentin
2003-02-04 19:59       ` Eli Zaretskii
2003-02-04 20:12         ` Kris Warkentin
2003-02-05  5:50           ` Eli Zaretskii
2003-02-04 22:02 ` Andrew Cagney
2003-02-05  1:29   ` Kris Warkentin
2003-02-05  2:40     ` Andrew Cagney
2003-02-05  2:59       ` Andrew Cagney
2003-02-05 12:31         ` Kris Warkentin
2003-02-05  2:55     ` Andrew Cagney
2003-02-05 17:15   ` Kris Warkentin
2003-02-05 18:46     ` Andrew Cagney
2003-02-07  1:48   ` Kris Warkentin
2003-02-07 19:22     ` Mark Kettenis
2003-02-07 20:08       ` Kris Warkentin
2003-02-07 21:59         ` Andrew Cagney
2003-02-11 18:11           ` Kris Warkentin
2003-02-11 18:41             ` patch to add HAVE_CONTINUABLE_BREAKPOINT to target_ops Kris Warkentin
2003-02-12 22:18       ` patch to add QNX NTO i386 support Kris Warkentin
2003-02-12 22:44         ` Daniel Jacobowitz
2003-02-13  0:52           ` Kris Warkentin
2003-02-13 22:21         ` Mark Kettenis
2003-02-13 22:29           ` Kris Warkentin
2003-02-13 22:53             ` Mark Kettenis
2003-02-13 23:55               ` Kris Warkentin
2003-02-14  0:01                 ` Kris Warkentin
2003-02-13 21:56       ` Kris Warkentin
2003-02-13 22:08         ` Daniel Jacobowitz
2003-02-13 22:25           ` Kris Warkentin
2003-02-13 22:29             ` Daniel Jacobowitz
2003-02-13 23:48               ` Kris Warkentin
2003-02-14  0:03                 ` Daniel Jacobowitz
2003-02-14  0:09                   ` Kris Warkentin
2003-02-14  0:13                     ` Daniel Jacobowitz
2003-02-14  0:35                       ` Kris Warkentin
2003-02-17 14:58                         ` Andrew Cagney
2003-02-17 15:44                           ` Daniel Jacobowitz
2003-02-17 16:45                             ` Andrew Cagney
2003-02-17 18:54                               ` Kris Warkentin
2003-02-18 21:26                                 ` Andrew Cagney
2003-02-18 22:30                                   ` Kris Warkentin
2003-02-20  0:42                                     ` Andrew Cagney
2003-02-27 19:02                             ` Kris Warkentin
2003-02-27 19:56                               ` Andrew Cagney
2003-02-27 20:02                               ` Daniel Jacobowitz
2003-02-27 20:10                                 ` Andrew Cagney
2003-02-27 20:11                                 ` Kris Warkentin
2003-02-27 20:23                                   ` Andrew Cagney
2003-02-27 20:28                                     ` Kris Warkentin [this message]
2003-02-05 20:48 ` Mark Kettenis
2003-02-05 21:23   ` Kris Warkentin
2003-02-05 21:43     ` Kris Warkentin
2003-02-05 22:24       ` Mark Kettenis
2003-02-06 15:13         ` Kris Warkentin
2003-02-06 18:19           ` Andrew Cagney
2003-02-05 22:48     ` Mark Kettenis
2003-02-06 15:08       ` Kris Warkentin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='035901c2de9e$c7a93770$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox