Thanks for the reply, I did download and build the valgrind version you
linked and the illegal instruction error went away, but instead I am
getting a segfault on the same place, as seen:
tobbe@archosaurus ~/projects/blocks (git)-[master] % valgrind ./bin/blocks
==7731== Memcheck, a memory error detector
==7731== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==7731== Using Valgrind-3.10.0.BETA2 and LibVEX; rerun with -h for
copyright info
==7731== Command: ./bin/blocks
==7731==
[12:25:39|script|VERBOSE]: Adding data/scripts/elephant.as for compilation.
[12:25:39|script|VERBOSE]: Adding data/scripts/general.as for compilation.
[12:25:39|script|VERBOSE]: Adding data/scripts/core/entity.as for
compilation.
[12:25:39|script|VERBOSE]: Adding data/scripts/core/loglevel.as for
compilation.
[12:25:39|script|VERBOSE]: Adding data/scripts/player.as for compilation.
[12:25:39|script|INFO]: Compiling scripts...
[12:25:40|script|INFO]: Compilation process over.
[12:25:40|script|VERBOSE]: Setting up script callbacks...
[12:25:40|script|VERBOSE]: Compilation process over.
[12:25:40|script|VERBOSE]: Done setting up callbacks.
[12:25:40|entity|INFO]: Loading entity definitions
[12:25:40|entity|INFO]: Found 2 entity definitions
[12:25:40|entity|VERBOSE]: Added entity type 'Elephant' to entity
definitions
[12:25:40|entity|VERBOSE]: Added entity type 'Player' to entity definitions
[12:25:40|entity|INFO]: Entity definitions loaded
[12:25:40|server|INFO]: Server initialised and ready to go
[12:25:40|script|VERBOSE]: Verbose message from the script
[12:25:40|script|INFO]: Info message from the script
[12:25:40|script|WARNING]: Warning message from the script
[12:25:40|script|ERROR]: Error message from the script
[12:25:40|script|INFO]: Game started!
[12:25:43|client|INFO]: client connected to server
==7731==
==7731== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==7731== General Protection Fault
==7731== at 0x5145EBB: __lll_unlock_elision (in /usr/lib/
libpthread-2.19.so)
==7731== by 0x441D31:
LocalClientConnectionListener::createClientConnection(LocalServerClientBridge*)
(in /home/tobbe/projects/blocks/bin/blocks)
==7731== by 0x4432D6: BlocksApplication::setupSinglePlayer() (in
/home/tobbe/projects/blocks/bin/blocks)
==7731== by 0x58ABA2E: fea::Application::run(int, char**) (in
/usr/local/lib/libfea-structure.so)
==7731== by 0x4497F5: main (in /home/tobbe/projects/blocks/bin/blocks)
==7731==
==7731== HEAP SUMMARY:
==7731== in use at exit: 31,353,847 bytes in 42,861 blocks
==7731== total heap usage: 120,444 allocs, 77,583 frees, 106,018,132
bytes allocated
==7731==
==7731== LEAK SUMMARY:
==7731== definitely lost: 426,836 bytes in 480 blocks
==7731== indirectly lost: 128 bytes in 1 blocks
==7731== possibly lost: 26,135,530 bytes in 39,957 blocks
==7731== still reachable: 4,791,353 bytes in 2,423 blocks
==7731== suppressed: 0 bytes in 0 blocks
==7731== Rerun with --leak-check=full to see details of leaked memory
==7731==
==7731== For counts of detected and suppressed errors, rerun with: -v
==7731== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6 from 1)
[5] 7731 segmentation fault valgrind ./bin/blocks
valgrind ./bin/blocks 7.64s user 0.11s system 99% cpu 7.760 total
This segfault does not happen without valgrind. Any ideas?
On 9 September 2014 22:57, Philippe Waroquiers <
philippe.waroqui...@skynet.be> wrote:
> On Tue, 2014-09-09 at 22:39 +0200, Tobias Widlund wrote:
>
> >
> > vex amd64->IR: unhandled instruction bytes: 0xF 0x1 0xD5 0x31 0xC0
> > 0xC3 0x48 0x8D
> > vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
> > vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F
> > vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
> > ==21008== valgrind: Unrecognised instruction at address 0x5146eb8.
> > ==21008== at 0x5146EB8: __lll_unlock_elision
> > (in /usr/lib/libpthread-2.19.so)
>
> That looks to be the use of the new 'transaction' instructions
> (xbegin etc).
> Assuming this is the case; you need the last 3.10 valgrind
> release (it is in beta status, see the announcement yesterday)
> Download from:
> http://www.valgrind.org/downloads/valgrind-3.10.0.BETA2.tar.bz2
>
> Philippe
>
>
>
>
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
