I didn't get a reply to my query in February, but I gather from the archives that... - setting the call_dummy_location to at_entry_point works except for functions which return structures or unions; - the gdb manual mentions a variable called call_scratch_address, but that doesn't seem to be actually present except on an AMD29000 platform, and - no other solution is currently known to the problem of calling a function from gdb when the stack is non-executable. I'd like to request the following. - Even if nothing else happens, please at least document this in the TODO file. - Add a configure option for non-executable stacks which (a) sets the call_dummy_location to at_entry_point and (b) makes gdb say "sorry, Dave, I can't do that" when you attempt to call a function which returns a structure or union. - How about implementing the call_dummy_location variable for all architectures (making it override the above behaviour if it is set)? Does this sound reasonable? Thanks. imc [please cc all replies]
