On Wed, Jan 14, 2004 at 12:06:13PM +1100, Ben Stringer wrote:
> On Wed, 2004-01-14 at 11:22, Leonard den Ottolander wrote:
> > Hi,
> >
> > Although I edited /etc/profile to set ulimit -c 100000
...
> > How do I enable core dumps under X so I can debug these crashes (or at
> > least upload a core file to bugzilla)?
> Did you ....
In a shell (existing gnome-terminal or xterm)
# ulimit -c 100000
or
# ulimit -c unlimited
Then invoke gnome-terminal by hand with strace watching it.
# strace -f -o /tmp/trace-gnome-terminal /usr/bin/gnome-terminal
If you are lucky you have an exception and learn something.
I did this and noted that gnome-terminal attempts to catch
most interesting signals.
3744 rt_sigaction(SIGSEGV, {0x2d3770, [], SA_RESTORER,...
3744 rt_sigaction(SIGABRT, {0x2d3770, [], SA_RESTORER,...
3744 rt_sigaction(SIGTRAP, {0x2d3770, [], SA_RESTORER,...
3744 rt_sigaction(SIGFPE, {0x2d3770, [], SA_RESTORER,...
3744 rt_sigaction(SIGBUS, {0x2d3770, [], SA_RESTORER,...
So next I took a chance and looked for help "/usr/bin/gnome-terminal --help"
"/usr/bin/gnome-terminal --usage" and I noticed these flags that may help.
--gdk-debug=FLAGS
--gtk-debug=FLAGS
--disable-crash-dialog
--g-fatal-warnings
With "strace" if you can discover the signal that is being caught
you can build a version that no longer traps that signal.
Perhaps "--disable-crash-dialog" is being remembered for some reason
by your desktop. I seem to recall a dialog box 100 years ago....
--
T o m M i t c h e l l
mitch48-at-sbcglobal-dot-net
