bug when stringify more then one tracepoint (one line patch)
josef ezra
jezra@emc.com
Mon May 2 18:57:00 GMT 2005
Hello Daniel
Thank you for checking my report.
The bug happens when user creates more then one memrange collection items.
I have tried to add a test to gdb.trace/collection.exp (the current one
collects one chunk of globals), but it keep complaining about “Current
target does not support trace”.
To follow collection.exp example, the commands:
(gdb) file collections
(gdb) target remote host_running_collection:9999
(gdb) trace globals_test_func
(gdb) actions
> collect globalc
> collect globald
> end
(gdb) tstart
Would send the target a string with arbitrary characters.
- Josef Ezra
Daniel Jacobowitz wrote:
> On Tue, Mar 01, 2005 at 03:06:56PM -0500, josef ezra wrote:
>
>>Hello
>>
>>In this code, since "count" accumulates the length of tracepoints
>>bytecode, adding it to "end" caused gaps of arbitrary data at the buffer.
>>
>>
>>2005-03-01 Josef Ezra <jezra@emc.com>
>> * tracepoint.c (stringify_collection_list): Correcting position of next
>>tracepoint to stringify at buffer.
>
>
> Hi Josef,
>
> Thanks for the patch. It looks correct to me; but could you describe
> how to trigger this bug?
>
More information about the Gdb-patches
mailing list