1 Mar 2005 05:46
Re: Hugin crashes just after startup
douglas wilkins <dgswilkins <at> yahoo.co.uk>
2005-03-01 04:46:02 GMT
2005-03-01 04:46:02 GMT
--- Edouard Gomez <edouard.gomez <at> gmail.com> wrote: > Ok it's now more than 2 weeks that i try to upgrade > my panoramic > toolchain and i can't get it working at all on my > SID box. First > it was some kind of obscure interaction of debian > gcc with panorama.h > file used in hugin, but even with that problem > resolved, i can't get > hugin starting. > > The thing that most annoy me, as a developper, is > that i can't get > anything from gdb/insight, because when i try to > debug then hugin just > forks so many childs at startup and strangely, gdb > detaches from all > processes and i can't see where it segfaults, i get > absolutly no line > number. If the segfault produces a core dump (it should) then: gdb hugin <core file name> should give it to you > > So i try to give as much information as i can, but > i'm sure that it's > not enough to get this fixed. >(Continue reading)
i forgot about core dumps because Debian SID
doesn't allow them by default.
So here it goes, the faulty call is in MainFrame.cpp:
#ifdef __unix__
splash = new wxSplashScreen(bitmap,
wxSPLASH_CENTRE_ON_SCREEN|wxSPLASH_NO_TIMEOUT,
0, NULL, -1, wxDefaultPosition,
wxDefaultSize,
wxSIMPLE_BORDER|wxSTAY_ON_TOP);
#else ...
I've put a DEBUG_INFO before this call and after, the second DEBUG_INFO
never gets called, so some data passed to the wxWidget function is
probably wrong.
Today it's already 1:30AM, so i'll just post this for now, i'l try to do
some more real debugging with insight in the next days, but no promise,
i'm quite busy with real life stuff
Hope this helps other devs to find what's wrong there.
On Wed, 2005-03-02 at 23:04 +0800, HaJo Schatz wrote:
> On Tue, 2005-03-01 at 16:42 -0600, Carl Wilhelm Soderstrom wrote:
>
> > I really would like that behavior back tho... seemed to make eminent sense.
> > :) (unless someone can suggest an even better way to do things, which is
> > likely possible).
> I actually appreciate the trend of gqview behaving the same way no
> matter where I got the focus. I found it quite disturbing not to be able
> to zoom/scroll via the keyboard if the focus was not on the picture
> itself. And setting the focus to the picture was difficult, as a click
> into the picture area advanced to the next picture already. Moving the
> focus by TAB is also not that convenient as you don't really get visual
> feedback when you reached the picture frame.
>
> But if scrolling up/down by "pages" is really necessary, maybe a [SHIFT|
> CTRL|ALT]-[PgDwn|PgUp] might make sense? It could be implemented with a
> similar behavior as say Mozilla/Firefox to have people get used to it
> quickly...
>
> HaJo
RSS Feed