This is the mail archive of the gdb@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: gdb command line option -e or -exec usage


Pedro Alves wrote:
On Friday 12 February 2010 18:45:01, Michael Snyder wrote:
Paragi, Ajeykumar B wrote:
Hi,

I have invoked gdb with '-e' command line option on an executable, The gdb manual says '-e' is used to set the executable to run.
But I could not see the symbols read in by gdb when I use -e and could
not insert breakpoints.


What is the intent of having the command line option "-e" or "-exec"?
Hmmm, it does seem to be broken.

It's not. `-e' is equivalent to "(gdb) exec-file". It doesn't read its argument for symbols, only for executable to run, or for pure memory contents.

You can get the same effect, though, by just leaving out the -e flag.

% gdb my-executable

That's equivalent to "(gdb) file", which is equivalent to "gdb -e my-executable -s my-executable", or just "gdb -se my-executable".


Right! Thanks, Pedro.



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