[Bug cli/17839] New: Add way to show frame size of each frame on stack

[Bug cli/17839] New: Add way to show frame size of each frame on stack

[dje at google dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=17839

            Bug ID: 17839
           Summary: Add way to show frame size of each frame on stack
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: cli
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

Sometimes it's nice to know how much stack space each frame is using.

Maybe "bt full" could be augmented to print frame addresses and sizes.
Or instead add a new option for this.

Or, a new utility command (in python?) to print frame addresses and sizes.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug cli/17839] Add way to show frame size of each frame on stack

[ssbssa at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=17839

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ssbssa at sourceware dot org

--- Comment #1 from Hannes Domani <ssbssa at sourceware dot org> ---
'info frame' shows a lot of info:
```
(top-gdb) info frame
Stack level 0, frame at 0x29f6e0:
 rip = 0x779514da in ntdll!ZwRequestWaitReplyPort; saved rip = 0x77801928
 called by frame at 0x29f710
 Arglist at 0x29f6d0, args:
 Locals at 0x29f6d0, Previous frame's sp is 0x29f6e0
 Saved registers:
  rip at 0x29f6d8
```

Not sure if this is good enough to close this ticket.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug cli/17839] Add way to show frame size of each frame on stack

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=17839

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
FWIW a lot of the "info frame" output is kind of stabs-specific
and not really relevant.  Like the "arglist" stuff is not useful.

There's also another bug somewhere about having gdb try to
decode a stack frame so you can see what all the bits are for.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug cli/17839] Add way to show frame size of each frame on stack

[ssbssa at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=17839

--- Comment #3 from Hannes Domani <ssbssa at sourceware dot org> ---
Right, PR9838, if that one were implemented, it would maybe qualify to close
this ticket as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug cli/17839] Add way to show frame size of each frame on stack

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=17839

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Tom Tromey from comment #2)
> FWIW a lot of the "info frame" output is kind of stabs-specific
> and not really relevant.  Like the "arglist" stuff is not useful.

I think there's a different bug about this, too.

-- 
You are receiving this mail because:
You are on the CC list for the bug.