From: Fei Ding <fdingiit@gmail.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Does GDB has 'quiet mode', and does GDB has APIs for writing log
Date: Mon, 30 Mar 2015 10:22:00 -0000 [thread overview]
Message-ID: <CAGmPkfJakLzMMt0e1wVarEO1iGz+ansRmV5P2et+g2AmHcS3gQ@mail.gmail.com> (raw)
In-Reply-To: <CAGmPkfLN7QMWNvEGY0ec2am-KikjT=BWxNxEwD8ku52CcY8y+w@mail.gmail.com>
The log's content and output file is up to me. For example I want to
log the message `breakpoint hit! EIP is 0x12345` into a file
`breakpoint.log` when a breakpoint is actually hit.
2015-03-30 17:57 GMT+08:00 Fei Ding <fdingiit@gmail.com>:
> I want to manually write log by myself, any APIs?
>
> 2015-03-30 16:09 GMT+08:00 Fei Ding <fdingiit@gmail.com>:
>> And I found
>>
>> https://sourceware.org/gdb/current/onlinedocs/gdb/Logging-Output.html#Logging-Output
>>
>> is helpful, I will check this out first.
>>
>> 2015-03-30 15:33 GMT+08:00 Fei Ding <fdingiit@gmail.com>:
>>> Hi all:
>>>
>>> I've modified GDB to support set breakpoints automatically according
>>> to a file containing all the EIP/RIP address that will be checked (a
>>> litter bit like `gdb -x file` command). But, the amount of breakpoints
>>> is too large, at least 10000, so I do not want to get any output like
>>> `Breakpoint 1, fun2 () at main.c:35` on my screen, I want GDB to be
>>> quiet at this time. Does GDB has something like `quiet mode`? Or, can
>>> I redirect these hints into a file?
>>>
>>> And, I want to write log when GDB is in `quiet mode`, does GDB has any
>>> APIs to support log?
>>>
>>> Thanks!
>>>
>>> BR.
next prev parent reply other threads:[~2015-03-30 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 7:33 Fei Ding
2015-03-30 8:09 ` Fei Ding
2015-03-30 9:57 ` Fei Ding
2015-03-30 10:22 ` Fei Ding [this message]
2015-03-30 14:44 ` Eli Zaretskii
2015-03-30 14:39 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGmPkfJakLzMMt0e1wVarEO1iGz+ansRmV5P2et+g2AmHcS3gQ@mail.gmail.com \
--to=fdingiit@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox