From ad9151c24fb1c305bcd9c90dfa9be5888144012b Mon Sep 17 00:00:00 2001 From: markj Date: Thu, 8 May 2014 03:33:54 +0000 Subject: Fix the rd_event_addr prototype and slightly clarify the use of the "event" parameter. MFC after: 3 days --- lib/librtld_db/librtld_db.3 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'lib') diff --git a/lib/librtld_db/librtld_db.3 b/lib/librtld_db/librtld_db.3 index 0c9a762..4645142 100644 --- a/lib/librtld_db/librtld_db.3 +++ b/lib/librtld_db/librtld_db.3 @@ -48,7 +48,7 @@ .Fc .Ft rd_err_e .Fo rd_event_addr -.Fa "rd_agent_t *rdap, rd_notify_t *notify" +.Fa "rd_agent_t *rdap, rd_event_e event, rd_notify_t *notify" .Fc .Ft rd_err_e .Fo rd_event_enable @@ -142,10 +142,10 @@ enables reporting of events. This function always returns RD_OK. .Pp .Fn rd_event_addr -returns the event address in the +returns the event address corresponding to the .Ft event parameter. -At the moment we only report RD_NOTIFY_BPT events. +At the moment we only report events of type RD_NOTIFY_BPT. .Pp .Fn rd_event_getmsg returns the message associated with the latest event. -- cgit v1.1