This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/18275] dprintf (call style) could automatically flush the standard output
- From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 29 Apr 2015 02:24:01 +0000
- Subject: [Bug breakpoints/18275] dprintf (call style) could automatically flush the standard output
- Auto-submitted: auto-generated
- References: <bug-18275-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18275
--- Comment #2 from Simon Marchi <simon.marchi at polymtl dot ca> ---
Hi Marc-AndrÃ,
Can you check if this small fix does the job for you? If it works, it would
need still need more work to make it parameterizable (if you want to flush or
not). Also, since you can customize what function dprintf calls, you might want
to flush another file than stdout, so maybe it should be configurable.
It could be similar to how "set dprintf-channel" works. It would be "set
dprintf-flush". If unset (the default), it wouldn't do anything. If it is set,
it would be evaluated as an expression and that value would be passed to
fflush. In your case, you would do "set dprintf-flush stdout".
What do you think?
Simon
--
You are receiving this mail because:
You are on the CC list for the bug.