Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* gdb command line option -e or -exec usage
       [not found]   ` <rt-3.4.5-8088-1265718123-322.550483-5-0@rt.gnu.org>
@ 2010-02-12  3:42     ` Paragi, Ajeykumar B
  2010-02-12 18:45       ` Michael Snyder
  0 siblings, 1 reply; 7+ messages in thread
From: Paragi, Ajeykumar B @ 2010-02-12  3:42 UTC (permalink / raw)
  To: gdb, gdb

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"?

Thanks & Regards,
Ajay

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: gdb command line option -e or -exec usage
  2010-02-12  3:42     ` gdb command line option -e or -exec usage Paragi, Ajeykumar B
@ 2010-02-12 18:45       ` Michael Snyder
  2010-02-12 18:58         ` Pedro Alves
  0 siblings, 1 reply; 7+ messages in thread
From: Michael Snyder @ 2010-02-12 18:45 UTC (permalink / raw)
  To: Paragi, Ajeykumar B; +Cc: gdb, gdb

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.

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

     % gdb my-executable



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: gdb command line option -e or -exec usage
  2010-02-12 18:45       ` Michael Snyder
@ 2010-02-12 18:58         ` Pedro Alves
  2010-02-12 19:10           ` Michael Snyder
  0 siblings, 1 reply; 7+ messages in thread
From: Pedro Alves @ 2010-02-12 18:58 UTC (permalink / raw)
  To: gdb; +Cc: Michael Snyder, Paragi, Ajeykumar B, gdb

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".

-- 
Pedro Alves


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: gdb command line option -e or -exec usage
  2010-02-12 18:58         ` Pedro Alves
@ 2010-02-12 19:10           ` Michael Snyder
  2010-02-12 20:08             ` Eli Zaretskii
  0 siblings, 1 reply; 7+ messages in thread
From: Michael Snyder @ 2010-02-12 19:10 UTC (permalink / raw)
  To: Pedro Alves; +Cc: gdb, Paragi, Ajeykumar B, gdb

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.


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: gdb command line option -e or -exec usage
  2010-02-12 19:10           ` Michael Snyder
@ 2010-02-12 20:08             ` Eli Zaretskii
  2010-02-15  3:58               ` Paragi, Ajeykumar B
  0 siblings, 1 reply; 7+ messages in thread
From: Eli Zaretskii @ 2010-02-12 20:08 UTC (permalink / raw)
  To: Michael Snyder; +Cc: pedro, gdb, ajeykumar.paragi, gdb

> Date: Fri, 12 Feb 2010 11:10:08 -0800
> From: Michael Snyder <msnyder@vmware.com>
> CC: "gdb@sourceware.org" <gdb@sourceware.org>,   "Paragi, Ajeykumar B" <ajeykumar.paragi@hp.com>,  "gdb@gnu.org" <gdb@gnu.org>
> 
> 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.

Are we missing something on the manual regarding this?


^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: gdb command line option -e or -exec usage
  2010-02-12 20:08             ` Eli Zaretskii
@ 2010-02-15  3:58               ` Paragi, Ajeykumar B
  2010-02-16 11:37                 ` Pedro Alves
  0 siblings, 1 reply; 7+ messages in thread
From: Paragi, Ajeykumar B @ 2010-02-15  3:58 UTC (permalink / raw)
  To: Eli Zaretskii, Michael Snyder; +Cc: pedro, gdb, gdb

Thank you!
Then why -e command line option is present when -se or gdb <exec-name> does the job.
Is it to load the symbol file which we like to..?

Regards,
Ajay

>-----Original Message-----
>From: Eli Zaretskii [mailto:eliz@gnu.org]
>Sent: Saturday, February 13, 2010 1:36 AM
>To: Michael Snyder
>Cc: pedro@codesourcery.com; gdb@sourceware.org; Paragi, Ajeykumar B;
>gdb@gnu.org
>Subject: Re: gdb command line option -e or -exec usage
>
>> Date: Fri, 12 Feb 2010 11:10:08 -0800
>> From: Michael Snyder <msnyder@vmware.com>
>> CC: "gdb@sourceware.org" <gdb@sourceware.org>,   "Paragi, Ajeykumar B"
><ajeykumar.paragi@hp.com>,  "gdb@gnu.org" <gdb@gnu.org>
>>
>> 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.
>
>Are we missing something on the manual regarding this?


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: gdb command line option -e or -exec usage
  2010-02-15  3:58               ` Paragi, Ajeykumar B
@ 2010-02-16 11:37                 ` Pedro Alves
  0 siblings, 0 replies; 7+ messages in thread
From: Pedro Alves @ 2010-02-16 11:37 UTC (permalink / raw)
  To: gdb; +Cc: Paragi, Ajeykumar B, Eli Zaretskii, Michael Snyder, gdb

On Monday 15 February 2010 03:57:36, Paragi, Ajeykumar B wrote:
> Then why -e command line option is present when -se or gdb <exec-name> does the job.
> Is it to load the symbol file which we like to..?

Yes.

-- 
Pedro Alves


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2010-02-16 11:37 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <RT-Ticket-550483@rt.gnu.org>
     [not found] ` <E2E3C92B1E0AB4468F79FC237074B248274A4CFFE8@GVW1116EXC.americas.hpqcorp.net>
     [not found]   ` <rt-3.4.5-8088-1265718123-322.550483-5-0@rt.gnu.org>
2010-02-12  3:42     ` gdb command line option -e or -exec usage Paragi, Ajeykumar B
2010-02-12 18:45       ` Michael Snyder
2010-02-12 18:58         ` Pedro Alves
2010-02-12 19:10           ` Michael Snyder
2010-02-12 20:08             ` Eli Zaretskii
2010-02-15  3:58               ` Paragi, Ajeykumar B
2010-02-16 11:37                 ` Pedro Alves

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox