All SDL apps require ^C to start before rendering [fbcon, Linux]

Hi all,

I’ve compiled libsdl to render to the framebuffer in Linux [vesafb, linux
2.6.17] and things are fine… almost. All SDL apps I’ve tried [many of the
demos from libsdl.org site] wait for a ^C before they start any rendering.

I haven’t done lots of investigating, and I’d thought I would ask if this is a
known issue before hunting down the offending lines in the code [this happens
on over a dozen different SDL demos I have tried].

pittsburgh:~# equery list sdl
[ Searching for package ‘sdl’ in all categories among: ]

  • installed packages
    [I–] [ ~] media-libs/libsdl-1.2.11 (0)
    [I–] [ ~] media-libs/sdl-image-1.2.4 (0)
    pittsburgh:~# uname -a
    Linux pittsburgh.i.cheek.com 2.6.17-gentoo #1 Sat Jul 8 13:52:06 EDT 2006 i686
    Intel® Celeron® CPU 2.00GHz GenuineIntel GNU/Linux

Thanks!

Joseph Cheek

I’ve compiled libsdl to render to the framebuffer in Linux [vesafb, linux
2.6.17] and things are fine… almost. All SDL apps I’ve tried [many of the
demos from libsdl.org site] wait for a ^C before they start any rendering.

It sounds like the fbcon code is blocking on a device open. You could try
putting printf() statements in the SDL fbcon initialization code to see how
far it’s getting…

See ya!
-Sam Lantinga, Senior Software Engineer, Blizzard Entertainment

Ah, printf(). That function has been single-handedly debugging my
applications since 1992.On 7/10/06, Sam Lantinga wrote:

I’ve compiled libsdl to render to the framebuffer in Linux [vesafb, linux
2.6.17] and things are fine… almost. All SDL apps I’ve tried [many of the
demos from libsdl.org site] wait for a ^C before they start any rendering.

It sounds like the fbcon code is blocking on a device open. You could try
putting printf() statements in the SDL fbcon initialization code to see how
far it’s getting…

::high five:: printf is the best

Someone should sell a shirt that says “I debug with printf mofo”> ----- Original Message -----

From: sdl-bounces+atrix2=cox.net@libsdl.org
[mailto:sdl-bounces+atrix2=cox.net at libsdl.org] On Behalf Of Andrew Kreps
Sent: Tuesday, July 11, 2006 1:56 PM
To: A list for developers using the SDL library. (includes SDL-announce)
Subject: Re: [SDL] all SDL apps require ^C to start before rendering
[fbcon,Linux]

Ah, printf(). That function has been single-handedly debugging my
applications since 1992.

On 7/10/06, Sam Lantinga wrote:

I’ve compiled libsdl to render to the framebuffer in Linux [vesafb,
linux

2.6.17] and things are fine… almost. All SDL apps I’ve tried [many of
the

demos from libsdl.org site] wait for a ^C before they start any
rendering.

It sounds like the fbcon code is blocking on a device open. You could try
putting printf() statements in the SDL fbcon initialization code to see
how
far it’s getting…


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl

I haven’t done lots of investigating, and I’d thought I would ask if this is a
known issue before hunting down the offending lines in the code [this happens
on over a dozen different SDL demos I have tried].

I’ve seen this before it doesn’t happen on the first run of the app
which is why I never fixed it as i only run my apps once :slight_smile:

but it seems to get stuck in a vt ioctl in SDL_fbevents.c, if you run
the app in a debugger, hit Ctrl-C and then bt you’ll see it.

Dave.