I'm trying to build a package for the xview library, and a few xview apps. 
Unfortunately, the apps that come with xview work fine, but third party apps
like olvwm and xvnews bomb out in the same way.

I built a debugging version of the lib, staticly linked everything, and now I
*still* get a backtrace that looks like this:

(gdb) bt
#0  0x20010280 in ?? ()
#1  0x188900 in ?? ()
#2  0x9578c in show_feedback (dp=0x192900, row=0x1d9480, event=0xefbfd468) at
p_list.c:3742
#3  0x95397 in set_current_row (dp=0x192900, event_row=0x1d9480,
event=0xefbfd468) at p_list.c:3533
#4  0x92f52 in panel_list_handle_event (item_public=1641664, event=0xefbfd468)
at p_list.c:1676

[many many lines of bt deleted]

No matter what I do.. those first two lines are allways ?? ().  Is it possibly
a call to libc that gdb isn't tracing into?  I'm running virgin 1.3 here on
i386.  Any pointers would be immensly helpful.  Both xvnews and olvwm generate
similar dumps, where the first two values are obscured.  

(that !@#$ debugging xview lib took 2 hours to build and generated a *24* meg
xvnews binary.  yike)

---
Tim Rightnour    -  root@garbled.net
http://www.zynetwc.com/~garbled/garbled.html