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: Tasks

On Thu, Jul 31, 2008 at 12:57 PM, Thiago Jung Bauermann
<> wrote:
> On Tue, 2008-07-29 at 13:46 -0600, Tom Tromey wrote:
>> >>>>> "Mark" == Mark Wielaard <> writes:
>> Mark> Maybe a nice "little" task to investigate is the catch syscall
>> Mark> support.  That might give someone a "simple" entry into the gdb
>> Mark> catch mechanism.  (little and simple in quotes, since I didn't
>> Mark> actually investigate myself much)
>> I think this is a very interesting idea.
>> Offhand I would say, those of us at Red Hat already have a full list
>> with stuff just directly related to C++.  Maybe somebody else could
>> implement this :-)
> I'm considering this. For a first step, we could catch the syscall but
> not interpret the arguments.
> There's the question of how GDB would know about the syscall arguments.
> Kernel debuginfo? That's the cleanest solution I think. But I don't know
> if such debuginfo exists today.

I can imagine there being multiple applications that would like this
info.  Can we start our own libstrace (or some such) and have gdb use

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