Control: forwarded -1 http://bugzilla.libsdl.org/show_bug.cgi?id=1905
2013/5/11 Bas Wijnen :
> (gdb) bt
> #0 0xb7fde424 in __kernel_vsyscall ()
> #1 0xb7c9882f in raise () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
> #2 0xb7c9bcf3 in abort () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
> #3
On Thu, May 09, 2013 at 02:46:30PM +0100, Manuel A. Fernandez Montecelo wrote:
> I added a -dbg package now (unstable), can you please try to reproduce
> the problem and get a back trace?
Sure. I've pasted a full session log below. The usable backtrace is
at the end.
Thanks,
Bas
$ gdb freedink
Hi,
I added a -dbg package now (unstable), can you please try to reproduce
the problem and get a back trace?
Cheers.
--
Manuel A. Fernandez Montecelo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debia
On 06-01-13 21:42, Manuel A. Fernandez Montecelo wrote:
> 2013/1/6 Bas Wijnen :
>>> I tried to use the "save4.dat" but the hero doesn't appear in front of
>>> any cave, but inside castle walls, with "screen locked", and I have to
>>> kill monsters through walls (!?!?) so the screen unlocks and I ca
2013/1/6 Bas Wijnen :
>> I tried to use the "save4.dat" but the hero doesn't appear in front of
>> any cave, but inside castle walls, with "screen locked", and I have to
>> kill monsters through walls (!?!?) so the screen unlocks and I can get
>> out of the castle. Still, no caves.
>
> The instruc
Hi,
On 06-01-13 19:28, Manuel A. Fernandez Montecelo wrote:
> I was trying to investigate the problem but didn't get very far.
Thanks for the effort.
> I tried to use the "save4.dat" but the hero doesn't appear in front of
> any cave, but inside castle walls, with "screen locked", and I have to
Hi,
2012/12/3 Bas Wijnen :
> I'm usually hesitant to assign a bug to a library, because it often
> happens that the actual bug is in the calling code. This is even more
> likely with freedink, which originates from code with lots of bugs.
>
> However, in this case I think I really did hit a bug in
This message was meant for the bug itself as well (instead of the
wrongly written package address).
Original Message
Subject: Re: [Bug-freedink] Bug#694260: freedink: Stack corruption
Date: Mon, 03 Dec 2012 10:02:23 +0100
From: Bas Wijnen
Organization: Debian
To: Luiji Maryo
You should probably send that MIDI file to the SDL_Mixer developers as well
so that they can look over it for something that would cause this type of
fault.
On Sun, Dec 2, 2012 at 2:20 PM, Bas Wijnen wrote:
> Hi,
>
> What I have found out so far:
>
> - It crashes when it makes the call to play
Hi,
What I have found out so far:
- It crashes when it makes the call to play the midi file.
- It doesn't crash when 20.mid is not present, nor when it is replaced
by a different midi file. (even though 20.mid plays without a problem
with timidity).
However, a really slim test case with only cal
Additional info :
- No crash when run with '-s' (no sound), so looks like this comes
from SDL_Mixer indeed.
- I think I tested this D-Mod already during the FreeDink development,
as I remembered it was a good test case for "bug-compatibility"
(ahem), abeilt maybe only the Lava part.
- Sylv
Hi,
According to the backtrace, it looks like it's in the SDL_mixer
thread indeed.
Cheers!
Sylvain
On Sat, Dec 01, 2012 at 12:38:17AM +0100, Bas Wijnen wrote:
> After a lot of debugging, the problem seems to be in libSDL instead. If
> I manage to get a simple test program triggering the bug, I'l
After a lot of debugging, the problem seems to be in libSDL instead. If
I manage to get a simple test program triggering the bug, I'll report it
there and close this bug. Until I do, I'll leave it open on freedink,
because I'm still not entirely sure.
Thanks,
Bas
On 24-11-12 21:08, Bas Wijnen wro
13 matches
Mail list logo
