Louis LeBlanc <[EMAIL PROTECTED]> writes: > On 01/11/03 09:57 AM, Dan Espen sat at the `puter and typed: > > Well, even though I'm not right all the time, I think > > I can keep coming up with ideas. > > > > I suppose plain: > > > > + "xterm" Exec /usr/X11R6/bin/xterm > > > > doesn't work either? > > > > The abort is supposed to cause a core dump. > > Do you have ulimit set to allow core dumps? > > > > Do you have a core file? > > If so, do "file core". > > > > You could also try running the strace from a menu: > > > > + "xterm" Exec strace -f /usr/X11R6/bin/xterm 2>/tmp/strace.out > > > > Problem solved. Turns out something went south in my latest update, > and my /dev/null wound up with the wrong permissions. When fvwm tries > to execute a command that has output from the menu, apparently it > redirects to /dev/null, and fails if there is any error. When it > couldn't write to /dev/null, it refused to start the process.
I don't see any redirection like that. > So, now we know. It wasn't fvwm, or xterm, but an update script for > an OS upgrade that hosed me. > > Thanks for your time! I'm curious. How did you find it? What was doing the abort? -- Dan Espen E-mail: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
