i build a daily snapshoot (20150327) on debian jessie
and i get this segfault:

(gdb) r
Starting program: /usr/bin/syncterm
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff08c6700 (LWP 3814)]
[New Thread 0x7fffebfff700 (LWP 3815)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff08c6700 (LWP 3814)]
__memcpy_sse2_unaligned ()
at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33
33 ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No existe el fichero o el directorio.
(gdb) bt
#0 __memcpy_sse2_unaligned ()
at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33
#1 0x000000000043d8be in bitmap_loadfont (filename=filename@entry=0x0)
at bitmap_con.c:715
#2 0x000000000043db74 in bitmap_init_mode (mode=mode@entry=3,
width=width@entry=0x899dc8 <bitmap_width>,
height=height@entry=0x899b88 <bitmap_height>) at bitmap_con.c:173
#3 0x0000000000438bb2 in sdl_init_mode (mode=mode@entry=3) at sdl_con.c:633
#4 0x0000000000438cf2 in sdl_init (mode=<optimized out>) at sdl_con.c:688
#5 0x000000000043b7b6 in sdl_initciolib (mode=<optimized out>)
at sdl_con.c:1933
#6 0x000000000042e09c in try_sdl_init (mode=<optimized out>) at
ciolib.c:127
#7 0x000000000042ea4a in initciolib (mode=<optimized out>) at ciolib.c:319
#8 0x000000000041d848 in CIOLIB_main (argc=1, argv=0x7fffffffe1b8)
at syncterm.c:1467
#9 0x000000000043b835 in sdl_run_main (data=data@entry=0x7fffffffe040)
at sdlfuncs.c:317
#10 0x00007ffff6a372f8 in SDL_RunThread (data=0x8d8af0)
at ./src/thread/SDL_thread.c:204
#11 0x00007ffff6a79e99 in RunThread (data=<optimized out>)
at ./src/thread/pthread/SDL_systhread.c:47
#12 0x00007ffff70700a4 in start_thread (arg=0x7ffff08c6700)
at pthread_create.c:309
---Type <return> to continue, or q <return> to quit---
#13 0x00007ffff6da504d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
(gdb)

Hi deuce!, have you seen this? i can not detect the problem but using
syncterm -iC works. Seems to be related with sdl

El 28/03/15 a las 14:30, Ragnarok escibió:

i build a daily snapshoot (20150327) on debian jessie
and i get this segfault:

(gdb) r
Starting program: /usr/bin/syncterm
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff08c6700 (LWP 3814)]
[New Thread 0x7fffebfff700 (LWP 3815)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff08c6700 (LWP 3814)]
__memcpy_sse2_unaligned ()
at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33
33 ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No existe el fichero o el directorio.
(gdb) bt
#0 __memcpy_sse2_unaligned ()
at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33
#1 0x000000000043d8be in bitmap_loadfont (filename=filename@entry=0x0)
at bitmap_con.c:715
#2 0x000000000043db74 in bitmap_init_mode (mode=mode@entry=3,
width=width@entry=0x899dc8 <bitmap_width>,
height=height@entry=0x899b88 <bitmap_height>) at bitmap_con.c:173
#3 0x0000000000438bb2 in sdl_init_mode (mode=mode@entry=3) at sdl_con.c:633 #4 0x0000000000438cf2 in sdl_init (mode=<optimized out>) at sdl_con.c:688
#5 0x000000000043b7b6 in sdl_initciolib (mode=<optimized out>)
at sdl_con.c:1933
#6 0x000000000042e09c in try_sdl_init (mode=<optimized out>) at
ciolib.c:127
#7 0x000000000042ea4a in initciolib (mode=<optimized out>) at ciolib.c:319 #8 0x000000000041d848 in CIOLIB_main (argc=1, argv=0x7fffffffe1b8)
at syncterm.c:1467
#9 0x000000000043b835 in sdl_run_main (data=data@entry=0x7fffffffe040)
at sdlfuncs.c:317
#10 0x00007ffff6a372f8 in SDL_RunThread (data=0x8d8af0)
at ./src/thread/SDL_thread.c:204
#11 0x00007ffff6a79e99 in RunThread (data=<optimized out>)
at ./src/thread/pthread/SDL_systhread.c:47
#12 0x00007ffff70700a4 in start_thread (arg=0x7ffff08c6700)
at pthread_create.c:309
---Type <return> to continue, or q <return> to quit---
#13 0x00007ffff6da504d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
(gdb)

Re: Re: syncterm crash
By: Ragnarok to Ragnarok on Sun Apr 05 2015 08:29 pm

Hi deuce!, have you seen this? i can not detect the problem but using syncterm -iC works. Seems to be related with sdl

Looks like the same bug that was reported against Windows and fixed on April 3rd. Please try the current snapshot and report back.

Thanks for the report!

---
http://DuckDuckGo.com/ a better search engine that respects your privacy.
þ Synchronet þ My Brand-New BBS (All the cool SysOps run STOCK!)

El 07/04/15 a las 03:34, Deuce escibió:

Re: Re: syncterm crash
By: Ragnarok to Ragnarok on Sun Apr 05 2015 08:29 pm

Hi deuce!, have you seen this? i can not detect the problem but using syncterm -iC works. Seems to be related with sdl

Looks like the same bug that was reported against Windows and fixed on April 3rd. Please try the current snapshot and report back.

Thanks for the report!

exactly same crash on debian jessie, i have this libraries:

libsdl-gfx1.2-5:amd64 v2.0.25-4
libsdl-image1.2:amd64 v1.2.12-5+b5
libsdl-mixer1.2:amd64 v1.2.12-11+b1
libsdl-net1.2:amd64 v1.2.8-4
libsdl-sound1.2:amd64 v1.0.3-7+b1
libsdl-ttf2.0-0:amd64 v2.0.11-3
libsdl1.2-dbg:amd64 v1.2.15-10+b1
libsdl1.2debian:amd64 v1.2.15-10+b1
libsdl2-2.0-0:amd64 v2.0.2+dfsg1-6
libsdl2-dbg:amd64 v2.0.2+dfsg1-6

Re: Re: syncterm crash
By: Ragnarok to Deuce on Tue Apr 07 2015 04:45 pm

Hi deuce!, have you seen this? i can not detect the problem but using syncterm -iC works. Seems to be related with sdl

Looks like the same bug that was reported against Windows and fixed on April 3rd. Please try the current snapshot and report back.

Thanks for the report!

exactly same crash on debian jessie, i have this libraries:

What was the date on the source directory on that system?

---
http://DuckDuckGo.com/ a better search engine that respects your privacy.
þ Synchronet þ My Brand-New BBS (All the cool SysOps run STOCK!)

El 09/04/15 a las 03:07, Deuce escibió:

Re: Re: syncterm crash
By: Ragnarok to Deuce on Tue Apr 07 2015 04:45 pm

Hi deuce!, have you seen this? i can not detect the problem but using syncterm -iC works. Seems to be related with sdl

Looks like the same bug that was reported against Windows and fixed on April 3rd. Please try the current snapshot and report back.

Thanks for the report!

exactly same crash on debian jessie, i have this libraries:

What was the date on the source directory on that system?

20150407, i use the syncterm-src.tgz from syncterm.bbsdev.net
maybe the tgz was not updated?
i will check it

El 09/04/15 a las 11:37, Ragnarok escibió:

El 09/04/15 a las 03:07, Deuce escibió:

Re: Re: syncterm crash
By: Ragnarok to Deuce on Tue Apr 07 2015 04:45 pm

Hi deuce!, have you seen this? i can not detect the problem but using
syncterm -iC works. Seems to be related with sdl

Looks like the same bug that was reported against Windows and fixed on >> > > April 3rd. Please try the current snapshot and report back.

Thanks for the report!

exactly same crash on debian jessie, i have this libraries:

What was the date on the source directory on that system?

20150407, i use the syncterm-src.tgz from syncterm.bbsdev.net
maybe the tgz was not updated?
i will check it

Hi Deuce, i'm search in my build historials and detect this:

20150210 works
20150303 begin the segfault

sorry that i do not have intermediate builds
i will try to diff between these dates.

Maybe, is possible that gcc was upgrade in these times..
actually have gcc 4.9 and sdl:

libsdl1.2-dev 1.2.15-10+b1
libsdl1.2debian:amd64 1.2.15-10+b1
libsdl2-2.0-0:amd64 2.0.2+dfsg1-6
libsdl2-dev 2.0.2+dfsg1-6

Re: Re: syncterm crash
By: Ragnarok to Ragnarok on Sun Apr 26 2015 05:12 pm

Hi Deuce, i'm search in my build historials and detect this:

20150210 works
20150303 begin the segfault

sorry that i do not have intermediate builds
i will try to diff between these dates.

Maybe, is possible that gcc was upgrade in these times..
actually have gcc 4.9 and sdl:

Can you do a debug build and get a backtrace of the crash?

---
http://DuckDuckGo.com/ a better search engine that respects your privacy.
þ Synchronet þ My Brand-New BBS (All the cool SysOps run STOCK!)

Can you do a debug build and get a backtrace of the crash?

yes, can i use extra option the get more/better/detailed debug?

(gdb) start
Temporary breakpoint 1 at 0x404160: file sdlfuncs.c, line 344.
Starting program: /tmp/buildd/syncterm-20150409+dfsg/src/syncterm/gcc.linux.x64.exe.debug/syncterm

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Temporary breakpoint 1, main (argc=1, argv=0x7fffffffdf68,
env=0x7fffffffdf78) at sdlfuncs.c:344
344 {
(gdb)
(gdb)
(gdb)
(gdb) n
358 load_sdl_funcs(&sdl);
(gdb)
354 ma.argc=argc;
(gdb)
356 ma.enviro=env;
(gdb)
344 {
(gdb)
358 load_sdl_funcs(&sdl);
(gdb)
348 int main_ret=0;
(gdb)
355 ma.argv=argv;
(gdb)
358 load_sdl_funcs(&sdl);
(gdb)
361 if(sdl.gotfuncs) {
(gdb)
389 if((!use_sdl_video) || ((getenv("REMOTEHOST")!=NULL || getenv("SSH_CLIENT")!=NULL) && getenv("DISPLAY")==NULL)) {
(gdb)
395 if(sdl.Init(SDL_INIT_VIDEO)==0) {
(gdb)
396 sdl_initialized=TRUE;
(gdb)
397 sdl_video_initialized=TRUE;
(gdb)
406 if(sdl_video_initialized && sdl.VideoDriverName(drivername,
sizeof(drivername))!=NULL) {
(gdb)
408 if((!strcmp(drivername, "caca")) || (!strcmp(drivername,"aalib"))
|| (!strcmp(drivername,"dummy"))) {
(gdb)
413 const SDL_VideoInfo *initial=sdl.GetVideoInfo();
(gdb)
416 if(initial)
(gdb)
417 sdl.initial_videoinfo=*initial; (gdb)
416 if(initial)
(gdb)
417 sdl.initial_videoinfo=*initial; (gdb)
420 sdl_video_initialized=TRUE;
(gdb)
425 SetThreadName("SDL Main");
(gdb)
426 atexit(QuitWrap);
(gdb)
427 sdl_main_sem=sdl.SDL_CreateSemaphore(0);
(gdb)
428 sdl_exit_sem=sdl.SDL_CreateSemaphore(0);
(gdb)
427 sdl_main_sem=sdl.SDL_CreateSemaphore(0);
(gdb)
428 sdl_exit_sem=sdl.SDL_CreateSemaphore(0);
(gdb)
429 main_thread=sdl.CreateThread(sdl_run_main,&ma);
(gdb)
428 sdl_exit_sem=sdl.SDL_CreateSemaphore(0);
(gdb)
429 main_thread=sdl.CreateThread(sdl_run_main,&ma);
(gdb)
[New Thread 0x7ffff09c3700 (LWP 24109)]
430 sdl.SemWait(sdl_main_sem);
(gdb)
429 main_thread=sdl.CreateThread(sdl_run_main,&ma);
(gdb)
430 sdl.SemWait(sdl_main_sem);
(gdb)
431 if(sdl_drawing_thread!=NULL) {
(gdb)
432 sdl_drawing_thread(NULL);
(gdb)
[New Thread 0x7fffebfff700 (LWP 24110)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff09c3700 (LWP 24109)]
0x00007ffff6d4f720 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)
Cannot find bounds of current function
(gdb)
Cannot find bounds of current function
(gdb) bt
#0 0x00007ffff6d4f720 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00000000004468be in bitmap_loadfont (filename=filename@entry=0x0)
at bitmap_con.c:715
#2 0x0000000000446b74 in bitmap_init_mode (mode=mode@entry=3, width=width@entry=0x8a2608 <bitmap_width>,
height=height@entry=0x8a23c8 <bitmap_height>) at bitmap_con.c:173
#3 0x0000000000441b92 in sdl_init_mode (mode=mode@entry=3) at sdl_con.c:633
#4 0x0000000000441cd2 in sdl_init (mode=<optimized out>) at sdl_con.c:690
#5 0x00000000004447b6 in sdl_initciolib (mode=<optimized out>) at sdl_con.c:1927
#6 0x000000000043707c in try_sdl_init (mode=<optimized out>) at
ciolib.c:127
#7 0x0000000000437a2a in initciolib (mode=<optimized out>) at ciolib.c:319
#8 0x0000000000424013 in CIOLIB_main (argc=1, argv=0x7fffffffdf68) at syncterm.c:1467
#9 0x0000000000444835 in sdl_run_main (data=data@entry=0x7fffffffddf0)
at sdlfuncs.c:317
#10 0x00007ffff6a372f8 in SDL_RunThread (data=0x8da080) at ./src/thread/SDL_thread.c:204
#11 0x00007ffff6a79e99 in RunThread (data=<optimized out>) at ./src/thread/pthread/SDL_systhread.c:47
#12 0x00007ffff70700a4 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#13 0x00007

Re: Re: syncterm crash
By: Ragnarok to Deuce on Mon Apr 27 2015 02:28 am

Can you do a debug build and get a backtrace of the crash?

yes, can i use extra option the get more/better/detailed debug?

Looks like I've found it. Appears to have been introduced with the four-font patch on Feb 27th, 2015.

---
http://DuckDuckGo.com/ a better search engine that respects your privacy.
þ Synchronet þ My Brand-New BBS (All the cool SysOps run STOCK!)

El 27/04/15 a las 06:07, Deuce escibió:

Re: Re: syncterm crash
By: Ragnarok to Deuce on Mon Apr 27 2015 02:28 am

Can you do a debug build and get a backtrace of the crash?

yes, can i use extra option the get more/better/detailed debug?

Looks like I've found it. Appears to have been introduced with the four-font
patch on Feb 27th, 2015.

i love you! works again!
=P