This is the mail archive of the 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]

Re: [PATCH 1/4] 'catch syscall' feature -- Architecture-independent part

On Wednesday 05 November 2008 19:08:49, Eli Zaretskii wrote:
> > From: Pedro Alves <>
> > Date: Wed, 5 Nov 2008 18:56:26 +0000
> > Cc:,
> >
> > 
> > What's wrong with "break ReadFile" ?
> Does it work for you?  

...  it does.  It's a function exported from a regular dll, just like
all other functions exported from other dlls.  I can only infer that
you haven't gone through the trouble of trying it yourself.

> And if the breakpoint breaks, can you easily 
> see the arguments of the call?

No, but that's not different from breaking on any other function
in any other system when you don't have debug info for it.
To solve this, the real solution is to make GDB make use
of MSFT's PDB debug info, not to somehow make up a new method
to extract arguments from plain regular code.

This is *no different* from breaking on the "read" function in
on linux, without debug info for  Eventually the libc
'read' function calls the real 'read' syscall, just like on Windows.

Pedro Alves

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