On Wed, Mar 27, 2002 at 11:27:48AM +0100, fvwm-workers wrote: > On Wed, Mar 27, 2002 at 08:00:04AM +0100, Olivier Chapuis wrote: > > On Tue, Mar 26, 2002 at 09:21:06PM +0000, Mikhael Goikhman wrote: > > > I get core dumps. The problem is that the stack trace is unusible. > > > gdb complains about "DW_FORM_strp pointing outside of .debug_str section" > > > and gives ??? in the stack. > > > > > > Maybe others may reproduce these core dumps and get a good stack. > > > > > > 1) Simply run kcalc shipped with kdeutils-2.2 -> core dump. > > > I have all feature supports on (except for multibyte). > > > > > > > So you compile fvwm with --disable-multibyte (it seems that > > now multibyte is on by default). > > > > When I run kcalc I get the following core dump: > > > > [EMAIL PROTECTED] graphviz-1.7.15]$ gdb /opt/fvwm/bin/fvwm2 ~/core > > GNU gdb 4.18 > > Core was generated by `fvwm2 -f themes-rc'. > > at misc.c:394 > > #4 0x80725f9 in GetWindowSizeHints (tmp=0x818f9f0) at add_window.c:2655 > > Damn, that's because fvwm_msg is called with > > fvwm_msg(..., "...%s...", tmp->name); > > But tmp->name is a structure, not a string. gcc doesn't complain > about that because it doesn't know that fvwm_msg uses printf > syntax. I guess there are dozens of similar places in the code. > Is there any way to inform gcc about the fvwm_msg syntax?
Ignore me. We already have this in the code - it had only to be enabled for fvwm_msg too. Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
