Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ross Morley <ross@tensilica.com>
To: Marc Gauthier <marc@tensilica.com>
Cc: Daniel Jacobowitz <drow@false.org>,
	  Nick Roberts <nickrob@snap.net.nz>,
	 Maxim Grigoriev <maxim@tensilica.com>,
	 gdb@sourceware.org,   Pete MacLiesh <pmac@tensilica.com>
Subject: Re: Understanding GDB frames
Date: Tue, 22 May 2007 17:20:00 -0000	[thread overview]
Message-ID: <46532642.1030501@tensilica.com> (raw)
In-Reply-To: <KAEOLFIOAJBBAFKHIDEAMENFEEAA.marc@tensilica.com>


Marc Gauthier wrote:

>Ross Morley wrote:
>  
>
>>Associating them with the function has problems with recursion. 
>>It seems to
>>me the ideal is to recreate vars that have gone out of scope (they really
>>are new vars). Use of a scope breakpoint can better detect that than the
>>current methods. However, are there implementation or performance issues?
>>    
>>
>
>As we discussed offline yesterday, this has performance implications
>on the GUI, which would have to recreate the varobjs every time which
>is time consuming.  
>

> And (a) being optional, could be fully supported
>like watchpoints by setting a breakpoint at the return PC, even though
>it has a performance hit (especially in the presence of recursion).
>
>  
>

I believe the performance implication comes mainly from the MI client
having to recreate the MI vars, not so much from the scope breakpoint.
If I recall correctly, the scope breakpoint would disappear the first
time the var went out of scope, and would not exist subsequent times
until the target stops and is resumed again (however it's been a while
since I looked at scope breakpoints).

Ross


  parent reply	other threads:[~2007-05-22 17:20 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 22:24 Maxim Grigoriev
2007-05-21 23:28 ` Ross Morley
2007-05-22  2:05   ` Nick Roberts
2007-05-22  2:31     ` Daniel Jacobowitz
2007-05-22  2:51       ` Nick Roberts
2007-05-22 10:58         ` Daniel Jacobowitz
2007-05-22  8:40       ` Ross Morley
2007-05-22 16:10         ` Marc Gauthier
2007-05-22 16:36           ` Daniel Jacobowitz
2007-05-22 18:14             ` Vladimir Prus
2007-05-22 18:33             ` Jim Ingham
2007-05-22 18:36               ` Daniel Jacobowitz
2007-05-23 21:45                 ` Jim Blandy
2007-05-22 17:20           ` Ross Morley [this message]
2007-05-22 20:24           ` Nick Roberts
2007-05-22 21:12             ` Maxim Grigoriev
2007-05-22  1:40 ` Joel Brobecker
2007-05-22  2:29 ` Daniel Jacobowitz
2007-05-22 18:37 ` Jim Blandy
2007-05-22 19:17   ` Maxim Grigoriev
2007-05-22 20:25     ` Nick Roberts
2007-05-22 20:33       ` Ross Morley
2007-05-22 20:45       ` Maxim Grigoriev
2007-05-22 21:26         ` Nick Roberts
2007-05-23  7:00           ` Eli Zaretskii
2007-05-23 10:48             ` Daniel Jacobowitz
2007-05-23 12:44               ` Eli Zaretskii
2007-05-22 23:56     ` Jim Blandy
2007-05-23  1:01       ` Maxim Grigoriev
2007-05-23  2:24         ` Daniel Jacobowitz
2007-05-23 16:37           ` Maxim Grigoriev
2007-05-23  0:05     ` Jim Blandy
2007-05-23  0:17       ` Daniel Jacobowitz
2007-05-23  0:17       ` Ross Morley
2007-05-23  0:32         ` Jim Blandy
2007-05-23  2:24           ` Ross Morley
2007-05-23 21:52             ` Jim Blandy
2007-05-24  0:05               ` Ross Morley
2007-05-24  1:24                 ` Ross Morley
2007-05-24 21:56                   ` Jim Blandy

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=46532642.1030501@tensilica.com \
    --to=ross@tensilica.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=marc@tensilica.com \
    --cc=maxim@tensilica.com \
    --cc=nickrob@snap.net.nz \
    --cc=pmac@tensilica.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