This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

testsuite/1240: Test gdbarch_frame_num_args


>Number:         1240
>Category:       testsuite
>Synopsis:       Test gdbarch_frame_num_args
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    unasigned
>State:          open
>Class:          test-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jun 09 14:58:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     ac131313@redhat.com
>Release:        2003-06-09
>Organization:
>Environment:
VAX and ns32k.
>Description:
(I'm guessing here, I don't have access to either a VAX or ns32k)

GDB has a mechanism for printing hidden arguments.  For instance, given the declaration/call:

void varargsfunc (a, ...)
...
  varargsfunc (1, 2, 3, 4, 0);

``info frame'' in varargsfunc() prints out not just "a" but also the additional unknown parameters "2", "3", "4", and "0".

There should be a testcase to exercise this.  Most ABIs could then xfail the test (it's a bug, not in GDB but in the eXternal ABI that can't be fixed) clearly specifying that it isn't possible to support the feature.

 
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]