Re: SableVM on ARM Zaurus

On Wed, Jan 12, 2005 at 07:24:33AM +0100, Cortez The Killer wrote:
> > The other option is to attach get a stack trace somehow. Either
> > by running sablevm under gdb until it segfaults and then getting
> > backtrace ('bt'), or asking it to drop core and then using gdb to
> > analyze it and get the backtrace.
> > 
> > I only guess the segfault might be happening ie. in GTK code that
> > does not handle some error gracefully, because of something that
> > never happens on standard GTK installations on desktop machines.
> 
> I haven't used gdb before, so it could take some time before I know
> how to use it. I guess you're right about the error being GTK related.
> I used this example program because it uses most of the standard GUI
> controls. If these examples work, I guess the system is stable enough
> to do GUI programming. That's what I needed to know.
> 

Hi,

It is easy to find segfault location with gdb.  If the gtk code has been
compiled with debbugging symbols (-g) which should be the case,

gdb --args PROGRAM ARGUMENTS

Then at the gdb prompt, type:
run

Then when it segfaults (gdb will tell you):
bt


David

---

David Bélanger
Web page:   http://www.cs.mcgill.ca/~dbelan2/
Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt