Very Computer

1. C Stack Frames with Sun and gcc

I've a question about the stack layout on a Sun (SunOS4.1.1)
for a C program compiled with gcc (2.6.1)

I've got a bug that only shows up when I compile with -O.
Since there's no debug info, debugging can be a real pain.
I can find global data and so forth using nm to give me
a symbol table listing, but this doesnt help me with
stack variables.

I'm doing post-mortems on the core file with gdb (4.13) and
I know I can look at the stack pointer, but I dont know
how gcc builds stack frames, so I cant follow the stack to
look at stack variables in routines higher up in the call tree.

Using printf() is not an option (for a number of reasons).

Any help is appreciated whether it be an explanation or a
pointer to some kind of documentation.

--Chuck

2. NIC compatability

3. gdb: missing frames in frame stack or function name garbled

4. High level design "chief" seeks "indians"

5. Bogus end() stack frames under Linux

6. dlink nics and linux

7. Frame Relay stack on Linux

8. aha1542b scsi controller as secondary controller

9. stack frames under linux x86

10. What's difference between task frame and memory layout?

11. RS/6000 subroutine linkage, stack layout and register saving

12. Stack Layout in Solaris

13. RS/6000 subroutine linkage and stack layout -- questions