octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wait_for_file ?? [print via pipes - help testing on Windows?]


From: bpabbott
Subject: Re: wait_for_file ?? [print via pipes - help testing on Windows?]
Date: Thu, 23 Sep 2010 14:37:12 +0000 (GMT)

On Sep 23, 2010, at 08:52 AM, Marco Atzeri <address@hidden> wrote:

--- Gio 23/9/10, Ben Abbott <address@hidden> ha scritto:

> On Sep 22, 2010, at 2:33 PM, Marco
> Atzeri wrote:
>
> > --- Mer 22/9/10, bpabbott <address@hidden>
> ha scritto:
> > When you say "octave segfaults" does octave continue
> running? I ask because I occasionally see "Segmentation
> fault" (Ubuntu via VirutalBox) but it's not Octave
> displaying it because, Octave continues to run. Perhaps it
> is gs, fig2dev, epstool, or something else?
> >
> > Ben
> >
> > octave crashs and stops to work
> > Marco
> >
>
> I assume the problem is with OpenGL. Perhaps it is best to
> attempt to check.
>
> Please try running Octave from inside gdb.
>
>     ./run-octave -g
>
> And then run the printing tests. After the segmentation
> fault, type "bt". We should be able to see where the crash
> occurred.
>
> Ben
>

octave:4> test_printing("fltk","-djpg")
test_printing("fltk","-djpg")
[New thread 6120.0x97c]
backend is fltk
print fltk-jpg -djpg
[New thread 6120.0x162c]

Program exited with code 030000000005.
(gdb) bt
No stack.
(gdb)

Marco
 
I forgot to mention, you'll need to add the debugging info by including "-g" when compiling Octave.

Ben


reply via email to

[Prev in Thread] Current Thread [Next in Thread]