This is the mail archive of the mailing list for the Archer 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]

Re: Syscall tracing

Ok, let me see if I understood this correctly...

On Thu, 2008-07-31 at 19:28 -0700, Roland McGrath wrote:
> To pretty-print an object of a type defined by some DSO, for the first
> piece we use the DWARF type descriptions that encode the ABI's layout,
> names, and types.  I'd always figured this is the right thing to do for the
> syscall ABI too.  This enables not just pretty-printing, but using the
> details in expression evaluation, GUI data inspectors, etc.

So with your approach there's no need to augment DWARF with special
attributes like Daniel suggested, right? The semantic intelligence would
be in the pretty-printer...

> So that unifies the second piece with the general pretty-printing issue.
> The kernel delivering its syscall ABI and how to make that pretty is just
> like some user libraries delivering its DSO ABIs and how to make that data
> pretty.

This means that we would try to convince the kernel folks to provide
Python pretty-printers to GDB, right?
Thiago Jung Bauermann
IBM Linux Technology Center

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