[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn_client_log3() doesn't work as advertised

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2006-04-19 20:42:53 CEST

Stefan Küng <tortoisesvn@gmail.com> writes:

> The same happens with the SVN client on windows.
> But I suspect that it simply ignores the peg revision you pass on the
> command line - you'll get the same if you don't pass it.
>
> The problem really is in the svn_client_log3() function.

Breakpoint 2, svn_client_log3 (targets=0x808c730, peg_revision=0xbffff8f4,
    start=0xbffffa5c, end=0xbffffa68, limit=100, discover_changed_paths=1,
    strict_node_history=0, receiver=0x8050c18 <log_message_receiver>,
    receiver_baton=0xbffff900, ctx=0x8087da0, pool=0x8068f38)
    at ../svn/subversion/libsvn_client/log.c:63
63 const char *base_name = NULL;
(gdb) p peg_revision[0]
$1 = {kind = svn_opt_revision_number, value = {number = 4, date = 4}}
(gdb) p start[0]
$2 = {kind = svn_opt_revision_number, value = {number = 2, date = 2}}
(gdb) p end[0]
$3 = {kind = svn_opt_revision_number, value = {number = 1, date = 1}}
(gdb) p ((char**)(targets[0].elts))[0]
$4 = 0x808c918 "wc/trunk/file2"

The peg revision appears to get as far as svn_client_log3.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 19 20:43:37 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.