[Mono-bugs] [Bug 395160] [Performance] Glyph map - loading glyphs is super slow.
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Thu Aug 14 14:07:35 EDT 2008
https://bugzilla.novell.com/show_bug.cgi?id=395160
User spouliot at novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395160#c5
--- Comment #5 from Sebastien Pouliot <spouliot at novell.com> 2008-08-14 12:07:34 MDT ---
The kill comes from valgrind itself and is caused by pulseaudio
==2549== Thread 11:
==2549== Conditional jump or move depends on uninitialised value(s)
==2549== at 0x21891606: (within /usr/lib64/libpulse.so.0.4.1)
==2549== by 0x218A49FE: (within /usr/lib64/libpulse.so.0.4.1)
==2549== by 0x218A5199: (within /usr/lib64/libpulse.so.0.4.1)
==2549== by 0x218812FE: (within /usr/lib64/libpulse.so.0.4.1)
==2549== by 0x218A6AC9: (within /usr/lib64/libpulse.so.0.4.1)
==2549== by 0x2188903C: pa_mainloop_dispatch (in
/usr/lib64/libpulse.so.0.4.1)
==2549== by 0x218892C5: pa_mainloop_iterate (in
/usr/lib64/libpulse.so.0.4.1)
==2549== by 0x2188937F: pa_mainloop_run (in /usr/lib64/libpulse.so.0.4.1)
==2549== by 0x2189377C: (within /usr/lib64/libpulse.so.0.4.1)
==2549== by 0x218AFE2F: (within /usr/lib64/libpulse.so.0.4.1)
==2549== by 0x4E3103F: start_thread (in /lib64/libpthread-2.8.so)
==2549== by 0x5A960CC: clone (in /lib64/libc-2.8.so)
vex amd64->IR: unhandled instruction bytes: 0xF 0xF 0xC1 0xB4
==2549== valgrind: Unrecognised instruction at address 0x1FBFB6F0.
==2549== Your program just tried to execute an instruction that Valgrind
==2549== did not recognise. There are two possible reasons for this.
==2549== 1. Your program has a bug and erroneously jumped to a non-code
==2549== location. If you are running Memcheck and you just saw a
==2549== warning about a bad jump, it's probably your program's fault.
==2549== 2. The instruction is legitimate but Valgrind doesn't handle it,
==2549== i.e. it's Valgrind's fault. If you think this is the case or
==2549== you are not sure, please let us know and we'll try to fix it.
==2549== Either way, Valgrind will now raise a SIGILL signal which will
==2549== probably kill your program.
This patch (from Rolf) disable it - and let [call|val]grind to its job
elsewhere.
Index: mplayer.cpp
===================================================================
--- mplayer.cpp (revision 110495)
+++ mplayer.cpp (working copy)
-323,6 +323,7 @@
switch (stream->GetType ()) {
case MediaTypeAudio:
+ break;
astream = (AudioStream *) stream;
audio.stream_count++;
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the mono-bugs
mailing list