trinity 1.6-2 source package in Ubuntu

Changelog

trinity (1.6-2) unstable; urgency=medium

  * Fix build issues on mips*. 
  * Upload to unstable.

 -- gustavo panizzo <email address hidden>  Thu, 17 Mar 2016 12:07:56 +0000

Upload details

Uploaded by:
gustavo panizzo
Uploaded to:
Sid
Original maintainer:
gustavo panizzo
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Xenial release universe misc

Downloads

File Size SHA-256 Checksum
trinity_1.6-2.dsc 1.9 KiB ab9842a53001327e075f3d28104c57f4cafb4bc507f510642d32fb93ea7e3cc7
trinity_1.6.orig.tar.xz 173.6 KiB e40efa320ddc814943e90be0386b5052ce0bbbc457b3f308fa973669d393a6d9
trinity_1.6-2.debian.tar.xz 217.8 KiB df74f102d1bf03ee2ee249a6346b2128795af5b0c416da50e5192883491d5d66

Available diffs

No changes file available.

Binary packages built by this source

trinity: No summary available for trinity in ubuntu zesty.

No description available for trinity in ubuntu zesty.

trinity-dbgsym: debug symbols for package trinity

 As 'fuzz testing' suggests, trinity calls syscalls at random, with random
 arguments. Where Trinity differs is that the arguments it passes are not
 purely random.
 .
 If a syscall took, for example, a file descriptor as an argument,
 one of the first things kernels does is validate that fd, if is not valid the
 kernel would just reject it as -EINVAL.
 .
 So on startup, Trinity creates a list of file descriptors, by opening pipes,
 scanning sysfs, procfs, /dev, and creates a bunch of sockets using random
 network protocols. Then when a syscall needs an fd, it gets passed one of
 these at random.
 .
 Trinity also shares those file descriptors between multiple threads, which
 causes havoc sometimes.
 .
 Warning: This program may seriously corrupt your files, including any of those
 that may be writable on mounted network file shares. It may create network
 packets that may cause disruption on your local network.
 Run at your own risk.