Re: InsetText Crash
Andre Poenitz schrieb:
On Fri, Mar 07, 2008 at 07:16:50PM -0500, rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still puzzled
about something. The crash is probably a consequence of my attempt to work
on Paragraph.cpp, but I'm not sure exactly what's happened. The backtrace
gives me a crash in the Layout constructor, and from there in basic_string.
So it looks as if there's an uninitialized string in the Layout object, but
I don't see how that could be. I think the the paragraph in question is
using emptyParagraphLayout, which is simply a static and otherwise
undefined Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar problems
elsewhere. If anyone has any ideas, I'd love to hear them.
Obviously, svn up -r 23548, then HelpLaTeX Configuration to generate the
crash.
Hm... this new 'Software Exception' dialog is pretty efficient at
creating useless stack traces.. *sigh*
That's why i needed some time to figure out the origin of the crash. Maybe it should be disabled in
debug mode?
bernhard
Andre'
Re: InsetText Crash
Bernhard Roider wrote:
Andre Poenitz schrieb:
On Fri, Mar 07, 2008 at 07:16:50PM -0500, rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still
puzzled about something. The crash is probably a consequence of my
attempt to work on Paragraph.cpp, but I'm not sure exactly what's
happened. The backtrace gives me a crash in the Layout constructor,
and from there in basic_string. So it looks as if there's an
uninitialized string in the Layout object, but I don't see how that
could be. I think the the paragraph in question is using
emptyParagraphLayout, which is simply a static and otherwise
undefined Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar
problems elsewhere. If anyone has any ideas, I'd love to hear them.
Obviously, svn up -r 23548, then HelpLaTeX Configuration to generate
the crash.
Hm... this new 'Software Exception' dialog is pretty efficient at
creating useless stack traces.. *sigh*
That's why i needed some time to figure out the origin of the crash.
Maybe it should be disabled in debug mode?
Yes, I'll do that.
Abdel.
Re: InsetText Crash
On Sat, Mar 08, 2008 at 12:45:37PM +0100, Bernhard Roider wrote:
Andre Poenitz schrieb:
On Fri, Mar 07, 2008 at 07:16:50PM -0500, rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still
puzzled about something. The crash is probably a consequence of my
attempt to work on Paragraph.cpp, but I'm not sure exactly what's
happened. The backtrace gives me a crash in the Layout constructor, and
from there in basic_string. So it looks as if there's an uninitialized
string in the Layout object, but I don't see how that could be. I think
the the paragraph in question is using emptyParagraphLayout, which is
simply a static and otherwise undefined Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar problems
elsewhere. If anyone has any ideas, I'd love to hear them.
Obviously, svn up -r 23548, then HelpLaTeX Configuration to generate the
crash.
Hm... this new 'Software Exception' dialog is pretty efficient at
creating useless stack traces.. *sigh*
That's why i needed some time to figure out the origin of the crash. Maybe
it should be disabled in debug mode?
I'd think so...
However, check with the Windows folks first, maybe the current situation
is better for them.
Andre'
Re: InsetText Crash
Andre Poenitz wrote:
On Sat, Mar 08, 2008 at 12:45:37PM +0100, Bernhard Roider wrote:
Andre Poenitz schrieb:
On Fri, Mar 07, 2008 at 07:16:50PM -0500, rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still
puzzled about something. The crash is probably a consequence of my
attempt to work on Paragraph.cpp, but I'm not sure exactly what's
happened. The backtrace gives me a crash in the Layout constructor, and
from there in basic_string. So it looks as if there's an uninitialized
string in the Layout object, but I don't see how that could be. I think
the the paragraph in question is using emptyParagraphLayout, which is
simply a static and otherwise undefined Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar problems
elsewhere. If anyone has any ideas, I'd love to hear them.
Obviously, svn up -r 23548, then HelpLaTeX Configuration to generate the
crash.
Hm... this new 'Software Exception' dialog is pretty efficient at
creating useless stack traces.. *sigh*
That's why i needed some time to figure out the origin of the crash. Maybe
it should be disabled in debug mode?
I'd think so...
However, check with the Windows folks first, maybe the current situation
is better for them.
There was no crash here, I had the exception message box displayed and
the buffer closed.
Abdel.
Re: InsetText Crash
On Sat, Mar 08, 2008 at 01:36:04PM +0100, Abdelrazak Younes wrote: [] There was no crash here, I had the exception message box displayed and the buffer closed. How do you get a backtrace in this situation? Andre'
Re: InsetText Crash
Andre Poenitz schrieb: On Sat, Mar 08, 2008 at 01:36:04PM +0100, Abdelrazak Younes wrote: [] There was no crash here, I had the exception message box displayed and the buffer closed. How do you get a backtrace in this situation? I am on windows also, and it is hard this way. If the exception is not caught and i start the program from within visual studio i can immediately debug with a call stack in a separate window, where i can click every line to jump to the code and inspect all the variables that are involved. bernhard
Re: InsetText Crash
Andre Poenitz wrote: On Sat, Mar 08, 2008 at 01:36:04PM +0100, Abdelrazak Younes wrote: [] There was no crash here, I had the exception message box displayed and the buffer closed. How do you get a backtrace in this situation? Well, I down need one, the message box tells me which inset is problematic. Isn't that what we want to know? Abdel.
Re: InsetText Crash
On Sat, Mar 08, 2008 at 03:59:35PM +0100, Abdelrazak Younes wrote: Andre Poenitz wrote: On Sat, Mar 08, 2008 at 01:36:04PM +0100, Abdelrazak Younes wrote: [] There was no crash here, I had the exception message box displayed and the buffer closed. How do you get a backtrace in this situation? Well, I down need one, the message box tells me which inset is problematic. Isn't that what we want to know? For the buffer-in-inset stuff, yes. But in general I'd like to have a backtrace pointing to the place where a segfault happened, not to the place where some event loop decided to pop up a dialog... Andre'
Re: InsetText Crash
Andre Poenitz wrote: On Sat, Mar 08, 2008 at 03:59:35PM +0100, Abdelrazak Younes wrote: Andre Poenitz wrote: On Sat, Mar 08, 2008 at 01:36:04PM +0100, Abdelrazak Younes wrote: [] There was no crash here, I had the exception message box displayed and the buffer closed. How do you get a backtrace in this situation? Well, I down need one, the message box tells me which inset is problematic. Isn't that what we want to know? For the buffer-in-inset stuff, yes. But in general I'd like to have a backtrace pointing to the place where a segfault happened, not to the place where some event loop decided to pop up a dialog... Agreed yes. And I changed that with an assertion there. Abdel.
Re: InsetText Crash
Andre Poenitz schrieb:
On Fri, Mar 07, 2008 at 07:16:50PM -0500, rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still puzzled
about something. The crash is probably a consequence of my attempt to work
on Paragraph.cpp, but I'm not sure exactly what's happened. The backtrace
gives me a crash in the Layout constructor, and from there in basic_string.
So it looks as if there's an uninitialized string in the Layout object, but
I don't see how that could be. I think the the paragraph in question is
using emptyParagraphLayout, which is simply a static and otherwise
undefined Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar problems
elsewhere. If anyone has any ideas, I'd love to hear them.
Obviously, svn up -r 23548, then Help>LaTeX Configuration to generate the
crash.
Hm... this new 'Software Exception' dialog is pretty efficient at
creating useless stack traces.. *sigh*
That's why i needed some time to figure out the origin of the crash. Maybe it should be disabled in
debug mode?
bernhard
Andre'
Re: InsetText Crash
Bernhard Roider wrote:
Andre Poenitz schrieb:
On Fri, Mar 07, 2008 at 07:16:50PM -0500, rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still
puzzled about something. The crash is probably a consequence of my
attempt to work on Paragraph.cpp, but I'm not sure exactly what's
happened. The backtrace gives me a crash in the Layout constructor,
and from there in basic_string. So it looks as if there's an
uninitialized string in the Layout object, but I don't see how that
could be. I think the the paragraph in question is using
emptyParagraphLayout, which is simply a static and otherwise
undefined Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar
problems elsewhere. If anyone has any ideas, I'd love to hear them.
Obviously, svn up -r 23548, then Help>LaTeX Configuration to generate
the crash.
Hm... this new 'Software Exception' dialog is pretty efficient at
creating useless stack traces.. *sigh*
That's why i needed some time to figure out the origin of the crash.
Maybe it should be disabled in debug mode?
Yes, I'll do that.
Abdel.
Re: InsetText Crash
On Sat, Mar 08, 2008 at 12:45:37PM +0100, Bernhard Roider wrote:
> Andre Poenitz schrieb:
>> On Fri, Mar 07, 2008 at 07:16:50PM -0500, rgheck wrote:
>>> I've fixed the crash reported by Bernhard at r23549. But I'm still
>>> puzzled about something. The crash is probably a consequence of my
>>> attempt to work on Paragraph.cpp, but I'm not sure exactly what's
>>> happened. The backtrace gives me a crash in the Layout constructor, and
>>> from there in basic_string. So it looks as if there's an uninitialized
>>> string in the Layout object, but I don't see how that could be. I think
>>> the the paragraph in question is using emptyParagraphLayout, which is
>>> simply a static and otherwise undefined Layout object:
>>>namespace {
>>>Layout const emptyParagraphLayout;
>>>}
>>> But why should this have an uninitialized member?
>>>
>>> Anyway, I'm quite puzzled by this and worried we'll find similar problems
>>> elsewhere. If anyone has any ideas, I'd love to hear them.
>>>
>>> Obviously, svn up -r 23548, then Help>LaTeX Configuration to generate the
>>> crash.
>> Hm... this new 'Software Exception' dialog is pretty efficient at
>> creating useless stack traces.. *sigh*
>
> That's why i needed some time to figure out the origin of the crash. Maybe
> it should be disabled in debug mode?
I'd think so...
However, check with the Windows folks first, maybe the current situation
is better for them.
Andre'
Re: InsetText Crash
Andre Poenitz wrote:
On Sat, Mar 08, 2008 at 12:45:37PM +0100, Bernhard Roider wrote:
Andre Poenitz schrieb:
On Fri, Mar 07, 2008 at 07:16:50PM -0500, rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still
puzzled about something. The crash is probably a consequence of my
attempt to work on Paragraph.cpp, but I'm not sure exactly what's
happened. The backtrace gives me a crash in the Layout constructor, and
from there in basic_string. So it looks as if there's an uninitialized
string in the Layout object, but I don't see how that could be. I think
the the paragraph in question is using emptyParagraphLayout, which is
simply a static and otherwise undefined Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar problems
elsewhere. If anyone has any ideas, I'd love to hear them.
Obviously, svn up -r 23548, then Help>LaTeX Configuration to generate the
crash.
Hm... this new 'Software Exception' dialog is pretty efficient at
creating useless stack traces.. *sigh*
That's why i needed some time to figure out the origin of the crash. Maybe
it should be disabled in debug mode?
I'd think so...
However, check with the Windows folks first, maybe the current situation
is better for them.
There was no crash here, I had the exception message box displayed and
the buffer closed.
Abdel.
Re: InsetText Crash
On Sat, Mar 08, 2008 at 01:36:04PM +0100, Abdelrazak Younes wrote: [] > There was no crash here, I had the exception message box displayed and the > buffer closed. How do you get a backtrace in this situation? Andre'
Re: InsetText Crash
Andre Poenitz schrieb: On Sat, Mar 08, 2008 at 01:36:04PM +0100, Abdelrazak Younes wrote: [] There was no crash here, I had the exception message box displayed and the buffer closed. How do you get a backtrace in this situation? I am on windows also, and it is hard this way. If the exception is not caught and i start the program from within visual studio i can immediately debug with a call stack in a separate window, where i can click every line to jump to the code and inspect all the variables that are involved. bernhard
Re: InsetText Crash
Andre Poenitz wrote: On Sat, Mar 08, 2008 at 01:36:04PM +0100, Abdelrazak Younes wrote: [] There was no crash here, I had the exception message box displayed and the buffer closed. How do you get a backtrace in this situation? Well, I down need one, the message box tells me which inset is problematic. Isn't that what we want to know? Abdel.
Re: InsetText Crash
On Sat, Mar 08, 2008 at 03:59:35PM +0100, Abdelrazak Younes wrote: > Andre Poenitz wrote: >> On Sat, Mar 08, 2008 at 01:36:04PM +0100, Abdelrazak Younes wrote: >> [] >>> There was no crash here, I had the exception message box displayed and >>> the buffer closed. >> How do you get a backtrace in this situation? > > Well, I down need one, the message box tells me which inset is problematic. > Isn't that what we want to know? For the buffer-in-inset stuff, yes. But in general I'd like to have a backtrace pointing to the place where a segfault happened, not to the place where some event loop decided to pop up a dialog... Andre'
Re: InsetText Crash
Andre Poenitz wrote: On Sat, Mar 08, 2008 at 03:59:35PM +0100, Abdelrazak Younes wrote: Andre Poenitz wrote: On Sat, Mar 08, 2008 at 01:36:04PM +0100, Abdelrazak Younes wrote: [] There was no crash here, I had the exception message box displayed and the buffer closed. How do you get a backtrace in this situation? Well, I down need one, the message box tells me which inset is problematic. Isn't that what we want to know? For the buffer-in-inset stuff, yes. But in general I'd like to have a backtrace pointing to the place where a segfault happened, not to the place where some event loop decided to pop up a dialog... Agreed yes. And I changed that with an assertion there. Abdel.
Re: InsetText Crash
One more clue: It's a docstring, basic_stringwchar_t, according ot gdb.
rh
rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still
puzzled about something. The crash is probably a consequence of my
attempt to work on Paragraph.cpp, but I'm not sure exactly what's
happened. The backtrace gives me a crash in the Layout constructor,
and from there in basic_string. So it looks as if there's an
uninitialized string in the Layout object, but I don't see how that
could be. I think the the paragraph in question is using
emptyParagraphLayout, which is simply a static and otherwise undefined
Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar
problems elsewhere. If anyone has any ideas, I'd love to hear them.
Obviously, svn up -r 23548, then HelpLaTeX Configuration to generate
the crash.
rh
Re: InsetText Crash
Ignore all of this: I finally figured out what the problem was.
rh
One more clue: It's a docstring, basic_stringwchar_t, according ot gdb.
rh
rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still
puzzled about something. The crash is probably a consequence of my
attempt to work on Paragraph.cpp, but I'm not sure exactly what's
happened. The backtrace gives me a crash in the Layout constructor,
and from there in basic_string. So it looks as if there's an
uninitialized string in the Layout object, but I don't see how that
could be. I think the the paragraph in question is using
emptyParagraphLayout, which is simply a static and otherwise
undefined Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar
problems elsewhere. If anyone has any ideas, I'd love to hear them.
Obviously, svn up -r 23548, then HelpLaTeX Configuration to generate
the crash.
rh
Re: InsetText Crash
On Fri, Mar 07, 2008 at 07:16:50PM -0500, rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still puzzled
about something. The crash is probably a consequence of my attempt to work
on Paragraph.cpp, but I'm not sure exactly what's happened. The backtrace
gives me a crash in the Layout constructor, and from there in basic_string.
So it looks as if there's an uninitialized string in the Layout object, but
I don't see how that could be. I think the the paragraph in question is
using emptyParagraphLayout, which is simply a static and otherwise
undefined Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar problems
elsewhere. If anyone has any ideas, I'd love to hear them.
Maybe the InsetText constructor constructs a paragraph that needs a
layout which in turn accesses parts of the non-yet-fully constructed
text ot paragraph.
Andre'
Re: InsetText Crash
On Fri, Mar 07, 2008 at 07:16:50PM -0500, rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still puzzled
about something. The crash is probably a consequence of my attempt to work
on Paragraph.cpp, but I'm not sure exactly what's happened. The backtrace
gives me a crash in the Layout constructor, and from there in basic_string.
So it looks as if there's an uninitialized string in the Layout object, but
I don't see how that could be. I think the the paragraph in question is
using emptyParagraphLayout, which is simply a static and otherwise
undefined Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar problems
elsewhere. If anyone has any ideas, I'd love to hear them.
Obviously, svn up -r 23548, then HelpLaTeX Configuration to generate the
crash.
Hm... this new 'Software Exception' dialog is pretty efficient at
creating useless stack traces.. *sigh*
Andre'
Re: InsetText Crash
One more clue: It's a docstring, basic_string, according ot gdb.
rh
rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still
puzzled about something. The crash is probably a consequence of my
attempt to work on Paragraph.cpp, but I'm not sure exactly what's
happened. The backtrace gives me a crash in the Layout constructor,
and from there in basic_string. So it looks as if there's an
uninitialized string in the Layout object, but I don't see how that
could be. I think the the paragraph in question is using
emptyParagraphLayout, which is simply a static and otherwise undefined
Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar
problems elsewhere. If anyone has any ideas, I'd love to hear them.
Obviously, svn up -r 23548, then Help>LaTeX Configuration to generate
the crash.
rh
Re: InsetText Crash
Ignore all of this: I finally figured out what the problem was.
rh
One more clue: It's a docstring, basic_string, according ot gdb.
rh
rgheck wrote:
I've fixed the crash reported by Bernhard at r23549. But I'm still
puzzled about something. The crash is probably a consequence of my
attempt to work on Paragraph.cpp, but I'm not sure exactly what's
happened. The backtrace gives me a crash in the Layout constructor,
and from there in basic_string. So it looks as if there's an
uninitialized string in the Layout object, but I don't see how that
could be. I think the the paragraph in question is using
emptyParagraphLayout, which is simply a static and otherwise
undefined Layout object:
namespace {
Layout const emptyParagraphLayout;
}
But why should this have an uninitialized member?
Anyway, I'm quite puzzled by this and worried we'll find similar
problems elsewhere. If anyone has any ideas, I'd love to hear them.
Obviously, svn up -r 23548, then Help>LaTeX Configuration to generate
the crash.
rh
Re: InsetText Crash
On Fri, Mar 07, 2008 at 07:16:50PM -0500, rgheck wrote:
>
> I've fixed the crash reported by Bernhard at r23549. But I'm still puzzled
> about something. The crash is probably a consequence of my attempt to work
> on Paragraph.cpp, but I'm not sure exactly what's happened. The backtrace
> gives me a crash in the Layout constructor, and from there in basic_string.
> So it looks as if there's an uninitialized string in the Layout object, but
> I don't see how that could be. I think the the paragraph in question is
> using emptyParagraphLayout, which is simply a static and otherwise
> undefined Layout object:
>namespace {
>Layout const emptyParagraphLayout;
>}
> But why should this have an uninitialized member?
>
> Anyway, I'm quite puzzled by this and worried we'll find similar problems
> elsewhere. If anyone has any ideas, I'd love to hear them.
Maybe the InsetText constructor constructs a paragraph that needs a
layout which in turn accesses parts of the non-yet-fully constructed
text ot paragraph.
Andre'
Re: InsetText Crash
On Fri, Mar 07, 2008 at 07:16:50PM -0500, rgheck wrote:
>
> I've fixed the crash reported by Bernhard at r23549. But I'm still puzzled
> about something. The crash is probably a consequence of my attempt to work
> on Paragraph.cpp, but I'm not sure exactly what's happened. The backtrace
> gives me a crash in the Layout constructor, and from there in basic_string.
> So it looks as if there's an uninitialized string in the Layout object, but
> I don't see how that could be. I think the the paragraph in question is
> using emptyParagraphLayout, which is simply a static and otherwise
> undefined Layout object:
>namespace {
>Layout const emptyParagraphLayout;
>}
> But why should this have an uninitialized member?
>
> Anyway, I'm quite puzzled by this and worried we'll find similar problems
> elsewhere. If anyone has any ideas, I'd love to hear them.
>
> Obviously, svn up -r 23548, then Help>LaTeX Configuration to generate the
> crash.
Hm... this new 'Software Exception' dialog is pretty efficient at
creating useless stack traces.. *sigh*
Andre'
