different developers.
An error cause contains information about the source location where the
-error occured, the actor involved in the error, and a message.
+error occurred, the actor involved in the error, and a message.
When you "catch" an error, that is, react to a function returning an
error status code without returning an error status code yourself,
[[field-src]]`src` vtype:[string]::
Source file path or name followed with `:LINE`, where `LINE` is the
- line number in this source file at which the event occured.
+ line number in this source file at which the event occurred.
+
Example: `user-config.c:1025`.
contain the source file and line number (see the <<field-src,`src`
field>>), but only the name of the nearest function symbol with an
offset in bytes to the location in the executable from which the LTTng
-event occured (see the <<field-func,`func` field>>).
+event occurred (see the <<field-func,`func` field>>).
If the executable file has neither ELF symbols nor DWARF information,
the {compcls} message iterator cannot map the event to its source
In all the cases above, the component adds a comment in the metadata
stream, above the field class, to indicate that a special translation
-occured.
+occurred.
=== Input message constraints
</dt>
<dd>
Called to check whether or not your \bt_msg_iter can currently
- seek a message occuring at or after a specific time given in
+ seek a message occurring at or after a specific time given in
nanoseconds from its
\ref api-tir-clock-cls-origin "clock class origin".
If you don't implement this method, then, if you implement the
\ref api-msg-iter-cls-meth-seek-ns "seek ns from origin" method, the
library assumes that your message iterator can always seek any
- message occuring at or after any time.
+ message occurring at or after any time.
The message iterator of a \bt_flt_comp will typically consider
the time seeking capability of its own upstream message
this method's implementation.
If you need to block the thread to compute whether or not your
- message iterator can seek a message occuring at or after a given
+ message iterator can seek a message occurring at or after a given
time, you can instead report to try again later to the caller by
returning
#BT_MESSAGE_ITERATOR_CLASS_CAN_SEEK_NS_FROM_ORIGIN_METHOD_STATUS_AGAIN.
bt_message_iterator_seek_ns_from_origin() uses this configuration
option and the beginning seeking capability of a message iterator
(bt_message_iterator_can_seek_beginning())
- to make it seek a message occuring at or after a specific time even
+ to make it seek a message occurring at or after a specific time even
when the message iterator does not implement the
\ref api-msg-iter-cls-meth-seek-ns "seek ns from origin" method.
</dt>
<dd>
Called within bt_message_iterator_seek_ns_from_origin() to make
- your message iterator seek a message occuring at or after a specific
+ your message iterator seek a message occurring at or after a specific
time given in nanoseconds from its
\ref api-tir-clock-cls-origin "clock class origin".
later.
If you need to block the thread to make your message iterator seek a
- message occuring at or after a given time, you can instead report to
+ message occurring at or after a given time, you can instead report to
try again later to the caller by returning
#BT_MESSAGE_ITERATOR_CLASS_SEEK_NS_FROM_ORIGIN_METHOD_STATUS_AGAIN.
@param[out] can_seek_ns_from_origin
<strong>On success</strong>, set \bt_p{*can_seek_ns_from_origin} to
#BT_TRUE if \bt_p{self_message_iterator} can currently seek a
- message occuring at or after \bt_p{ns_from_origin} nanoseconds from
+ message occurring at or after \bt_p{ns_from_origin} nanoseconds from
its \ref api-tir-clock-cls-origin "clock class origin".
@retval #BT_MESSAGE_ITERATOR_CLASS_CAN_SEEK_NS_FROM_ORIGIN_METHOD_STATUS_OK
<dt>
\anchor api-msg-iter-op-seek-ns
- Make the message iterator seek a message occuring at or after a
+ Make the message iterator seek a message occurring at or after a
given time (in nanoseconds) from its clock class origin
</dt>
<dd>
/*!
@brief
Returns whether or not the message iterator \bt_p{message_iterator}
- can currently seek a \bt_msg occuring at or after
+ can currently seek a \bt_msg occurring at or after
\bt_p{ns_from_origin} nanoseconds from its
\ref api-tir-clock-cls-origin "clock class origin".
Requested time point to seek.
@param[out] can_seek_ns_from_origin
<strong>On success</strong>, \bt_p{*can_seek_ns_from_origin} is
- #BT_TRUE if \bt_p{message_iterator} can seek a message occuring at
+ #BT_TRUE if \bt_p{message_iterator} can seek a message occurring at
or after \bt_p{ns_from_origin} nanoseconds from its clock class
origin.
@bt_pre_not_null{can_seek_ns_from_origin}
@sa bt_message_iterator_seek_ns_from_origin() —
- Makes a message iterator seek a message occuring at or after
+ Makes a message iterator seek a message occurring at or after
a given time from its clock class origin.
*/
/*!
@brief
Makes the message iterator \bt_p{message_iterator} seek a \bt_msg
- occuring at or after \bt_p{ns_from_origin} nanoseconds from its
+ occurring at or after \bt_p{ns_from_origin} nanoseconds from its
\ref api-tir-clock-cls-origin "clock class origin".
See \ref api-msg-iter-op-seek-ns "this operation's documentation".
\bt_p{message_iterator}, before you call this function.
@param[in] message_iterator
- Message iterator to seek to a message occuring at or after
+ Message iterator to seek to a message occurring at or after
\bt_p{ns_from_origin} nanoseconds from its clock class origin.
@param[in] ns_from_origin
Time point to seek.
@sa bt_message_iterator_can_seek_ns_from_origin() —
Returns whether or not a message iterator can currently seek a
- message occuring at or after a given time from its clock class
+ message occurring at or after a given time from its clock class
origin.
*/
extern bt_message_iterator_seek_ns_from_origin_status
stream's default clock.
In other words, a default clock snapshot contains the value of the
- stream's default clock when this message occured.
+ stream's default clock when this message occurred.
The default clock class property of a \bt_stream_cls is optional:
if a stream class has no default clock class, then its instances
of the stream's default clock.
In other words, a default clock snapshot contains the value of the
- stream's default clock when this message occured.
+ stream's default clock when this message occurred.
A clock snapshot is a \ref api-fund-unique-object "unique object": it
belongs to a \bt_msg.
\ref api-tir-clock-cls-origin "correlatable".
A typical use case for streams is to use one for each traced CPU. Then
-the messages related to a given stream are the ones which occured on a
+the messages related to a given stream are the ones which occurred on a
given CPU. Other schemes are possible: they are completely
application-specific, and \bt_name does not enforce any specific
stream arrangement pattern.
stream's default clock.
In other words, a default clock snapshot contains the value of the
- stream's default clock when this message occured.
+ stream's default clock when this message occurred.
To create a stream:
goto end;
error:
- /* That's how we indicate that an error occured */
+ /* That's how we indicate that an error occurred */
destroy_item_array(parse_ret.items);
parse_ret.items = NULL;
* #CTF_MSG_ITER_MEDIUM_STATUS_EOF on the \em following
* call.
* - <b>#CTF_MSG_ITER_MEDIUM_STATUS_ERROR</b>: A fatal
- * error occured during this operation. In this case, the
+ * error occurred during this operation. In this case, the
* message iterator function called by the user returns
* #CTF_MSG_ITER_STATUS_ERROR.
*
*/
if (stream->prev_packet_state.end_cs == UINT64_C(-1)) {
BT_COMP_LOGE("Incompatible discarded packets message "
- "occuring before the stream's first packet: "
+ "occurring before the stream's first packet: "
"stream-id=%" PRIu64 ", stream-name=\"%s\", "
"trace-name=\"%s\", path=\"%s/%s\"",
bt_stream_get_id(ir_stream),
/*
* Not supported: discarded events or discarded packets support
* without packets support. Packets are the way to know where
- * discarded events/packets occured in CTF 1.8.
+ * discarded events/packets occurred in CTF 1.8.
*/
if (!bt_stream_class_supports_packets(ir_sc)) {
BT_ASSERT(!bt_stream_class_supports_discarded_packets(ir_sc));
if (stream->packet_state.is_open &&
stream->sc->discarded_events_has_ts) {
BT_COMP_LOGE("Unsupported discarded events message with "
- "default clock snapshots occuring within a packet: "
+ "default clock snapshots occurring within a packet: "
"stream-id=%" PRIu64 ", stream-name=\"%s\", "
"trace-name=\"%s\", path=\"%s/%s\"",
bt_stream_get_id(ir_stream),
/*
* Check if the message of the current live stream
- * iterator occured at the exact same time or after the
+ * iterator occurred at the exact same time or after the
* last message returned by this component's message
* iterator. If not, we return an error.
*/
*
* @returns 1 on if the build id of stored in `bin` matches
* the build id of the ondisk file.
- * 0 on if they are different or an error occured.
+ * 0 on if they are different or an error occurred.
*/
static
int is_build_id_matching(struct bin_info *bin)
g_strdup_printf("%"PRId64, src_loc->line_no);
if (!debug_info_src->line_no) {
BT_COMP_LOGE_APPEND_CAUSE(self_comp,
- "Error occured when setting `line_no` field.");
+ "Error occurred when setting `line_no` field.");
goto error;
}
}
BT_LOG_WRITE(log_level, BT_LOG_TAG,
- "Exception occured: Python traceback:\n%s", exc->str);
+ "Exception occurred: Python traceback:\n%s", exc->str);
}
end:
projects / babeltrace.git / commitdiff
