LCDproc development and user support list

Text archives Help

[Lcdproc] Mysterious Driver Segfault

Chronological Thread 
  • From: monmotha AT (MonMotha)
  • Subject: [Lcdproc] Mysterious Driver Segfault
  • Date: Mon Aug 2 02:19:02 2004

The fault doesn't seem to be actually occuring in my code, though I'm
I'm probably tickling a bug somewhere else, or messing with data I shouldn't

I do have a backtrace:
(gdb) backtrace
#0 0x08055d13 in LL_Get (list=0x809c778) at LL.c:198
#1 0x08055dd3 in LL_GetNext (list=0x809c778) at LL.c:264
#2 0x08054a88 in drivers_string (x=1, y=4,
string=0xbffff87c " this hopeless mess.") at drivers.c:202
#3 0x08052cb2 in render_frame (list=0x809e010, fscroll=118, left=0, top=0,
right=20, bottom=4, fwid=20, fhgt=4, fspeed=10, timer=123) at
#4 0x08052411 in render_screen (s=0x809dfd8, timer=123) at render.c:121
#5 0x0804e69f in do_mainloop () at main.c:842
#6 0x0804d887 in main (argc=7, argv=0xbffffdb4) at main.c:249

This is current CVS HEAD BTW. Is there any way anyone can think of that my
could cause a segfault to occur at that point? It appears that at line 202
drivers.c, it has not yet called my string function yet, but rather is
through a linked list trying to call my driver's string function.


Archive powered by MHonArc 2.6.18.

Top of page