[ts-gen] Cross-session order modification and cancellation now works

[Nils Gebhardt]

Currently I get Seg faults when trying ./shim --data resp. shim --risk. 
Plain ./shim call results in a short help message end normal exit.
Calling from gdb it says 

Starting program: /home/n/T/TEST/shim-081121/shim --data
[Thread debugging using libthread_db enabled]
[New Thread 0x7f034da4f6f0 (LWP 19489)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f034da4f6f0 (LWP 19489)]
0x0000000000488548 in
TradingShimDaemon1_0::ObjectTypeSystem::Compound::Compound ()

-- not too much help I am afraid. 
Any suggestions? (Platform is ubuntu 8.04 64 bit, running previous
versions without complaints) 

Regards

Nils




On Fri, 2008-11-21 at 20:21 -0500, pippin at owlriver.net wrote:
> I've just pushed a new release to the ftp server.  See the NEWS file
> for details; in brief, as the subject line says:
> 
>     Cross-session order modification and cancellation now works;
>     see the script exs/kill.rb for an example.
> 
> This has been a long time coming, and I'd like interested parties to
> let the list know if, in its current simple form, it suits their needs.
> 
> There is related work in this area still to be done in the near future,
> and also some for furthur out.  Currently, the shim replays create and
> modify events from the journal, which provides bare-bones cross-session
> functionality.  Additional features might include:
> 
>     1. implementation of a "list order <key>" command, to query
>        for order status by order key; scripts could read keys from
>        the database, and query the shim for what it thought their
>        status to be.
> 
>     2. msg --- status, open order, and exec report --- replay, so
>        that the shim would know about quantity filled and the like,
>        so improving the order status query capability above; and
> 
>     3. error message analysis, so order state could track information
>        from order-related error messages.
> 
> The first is of immediate interest to us, and should follow along
> soon; the second, not sure; and the third, almost certainly not for
> a while.  Note that it is in some sense possible for the downstream
> to take responsibility for 1 -- 3 above, which is one reason that
> the last item doesn't have a higher priority.
> 
> I've shifted to developing with a 64bit build farm, and this and
> other infra-structure changes have taken up a good part of the last
> month.  As part of this effort, there have been a number of minor
> changes to our release process, and if you see problems in building
> a shim from the new release, please notify the list.
> 
> Note that make now dumps .o files in a subdirectory obj, and note
> also that log files now end up by default in a subdirectory log;
> see NEWS for details.
> 
> Thanks,
> 
> Bill
> _______________________________________________
> ts-general mailing list
> ts-general at trading-shim.org
> http://www.trading-shim.org/mailman/listinfo/ts-general