search for: lowermemargu

...ack and we call a function recursively. For example in the code when we have a int s; inside the struct instead of short s; gdb is able to print the structure value properly. The difference is when we have a short inside struct we are treating it as byval parameter object inside X86TargetLowering::LowerMemArgument were as when we have an "int" it doesn't treat it as byval. Thanks On Tue, Dec 4, 2012 at 9:26 PM, Relph, Richard <Richard.Relph at amd.com> wrote: > Karthik, > At what point within recurse() are you asking gdb to display the value of argument a? > What...

Karthik, At what point within recurse() are you asking gdb to display the value of argument a? What I'm wondering about is if the debug information gdb is using to get at a might not be correct at the particular point you are checking a, particularly if that is before the prolog has completed execution. The way debug information for arguments pushed on the stack is represented in

Hi All, I was debugging a clang binary when i found this problem. The following code is complied with clang. typedef struct s { short s; } SVAL; void recurse (SVAL a, int depth) { a.s = --depth; if (depth == 0) return; else recurse(a,depth); } int main () { SVAL s; s.s = 5; recurse (s, 5); return 0; } When i try to access value of a.s in function recurse through gdb(i.e