On 30-Apr-2002 Claus Hindsgaul wrote:
Sorry, no luck with the new patch
Ok thanks for the file I can recreate the crash with it and your explanation.
I fixed this now hopefully but there is IMO a greater problem to fix in GCItem.
(this is for Angus)
IMO that this function is wrong:
void
On Thursday 02 May 2002 10:44 am, Juergen Vigna wrote:
On 30-Apr-2002 Claus Hindsgaul wrote:
Sorry, no luck with the new patch
Ok thanks for the file I can recreate the crash with it and your
explanation. I fixed this now hopefully but there is IMO a greater problem
to fix in GCItem.
On 30-Apr-2002 Claus Hindsgaul wrote:
> Sorry, no luck with the new patch
Ok thanks for the file I can recreate the crash with it and your explanation.
I fixed this now hopefully but there is IMO a greater problem to fix in GCItem.
(this is for Angus)
IMO that this function is wrong:
void
On Thursday 02 May 2002 10:44 am, Juergen Vigna wrote:
> On 30-Apr-2002 Claus Hindsgaul wrote:
> > Sorry, no luck with the new patch
>
> Ok thanks for the file I can recreate the crash with it and your
> explanation. I fixed this now hopefully but there is IMO a greater problem
> to fix in
tir, 2002-04-30 kl. 17:47 skrev John Levon:
Can you please provide a screenshot. I've tried varying line lengths and
am unable to cause any problems
Sure.
This picture were made after:
* Opening LyX
* Deactivating Rescale bitmap fonts (so the bug351-file will
load)
tir, 2002-04-30 kl. 17:47 skrev John Levon:
> Can you please provide a screenshot. I've tried varying line lengths and
> am unable to cause any problems
Sure.
This picture were made after:
* Opening LyX
* Deactivating "Rescale bitmap fonts" (so the bug351-file will
On 29-Apr-2002 Claus Hindsgaul wrote:
By request, I have obtained the following backtraces from valgrind
(attached) and gdb from a LyX 1.2.0CVS of today with Juergens patch
applied compiled with --disable-optimization. They were both made doing
the same thing as in my prior backtraces.
Sorry, no luck with the new patch
But I found a very good lead!
The problem seems to be tied tightly to the line wrapping on the WYSIWYM
screen WHILE LOADING IMAGES.
* If I maximize the LyX window before opening the document, the
bug can
* Choosing Danish language
On Tue, Apr 30, 2002 at 03:08:18PM +0200, Claus Hindsgaul wrote:
* If I maximize the LyX window before opening the document, the
bug
... is not triggered.
Can you please provide a screenshot. I've tried varying line lengths and
am unable to cause any problems
thanks
On 29-Apr-2002 Claus Hindsgaul wrote:
> By request, I have obtained the following backtraces from valgrind
> (attached) and gdb from a LyX 1.2.0CVS of today with Juergens patch
> applied compiled with --disable-optimization. They were both made doing
> the same thing as in my prior backtraces.
Sorry, no luck with the new patch
But I found a very good lead!
The problem seems to be tied tightly to the line wrapping on the WYSIWYM
screen WHILE LOADING IMAGES.
* If I maximize the LyX window before opening the document, the
bug can
* Choosing Danish language
On Tue, Apr 30, 2002 at 03:08:18PM +0200, Claus Hindsgaul wrote:
> > * If I maximize the LyX window before opening the document, the
> > bug
> ... is not triggered.
Can you please provide a screenshot. I've tried varying line lengths and
am unable to cause any problems
On 24-Apr-2002 Claus Hindsgaul wrote:
ons, 2002-04-24 kl. 15:27 skrev John Levon:
Did that help?
No ! Look at the backtrace yourself then look at the source they are
completely different. Perhaps a valgrind bug ?
Thanks for your backtraces (and patience). Would it be possible for you to
man, 2002-04-29 kl. 15:42 skrev Juergen Vigna:
Thanks for your backtraces (and patience). Would it be possible for you to
apply the attached patch to an updated cvs version and see if that fixes the
problem for you?
Thank you for the patch. Unfortunately it did not avoid the crash. Would
you
Claus Hindsgaul [EMAIL PROTECTED] writes:
| man, 2002-04-29 kl. 15:42 skrev Juergen Vigna:
Thanks for your backtraces (and patience). Would it be possible for you to
apply the attached patch to an updated cvs version and see if that fixes the
problem for you?
| Thank you for the patch.
By request, I have obtained the following backtraces from valgrind
(attached) and gdb from a LyX 1.2.0CVS of today with Juergens patch
applied compiled with --disable-optimization. They were both made doing
the same thing as in my prior backtraces.
Claus Hindsgaul
gdb:
(gdb) run
Starting
On 24-Apr-2002 Claus Hindsgaul wrote:
> ons, 2002-04-24 kl. 15:27 skrev John Levon:
>> > Did that help?
>>
>> No ! Look at the backtrace yourself then look at the source they are
>> completely different. Perhaps a valgrind bug ?
Thanks for your backtraces (and patience). Would it be possible
man, 2002-04-29 kl. 15:42 skrev Juergen Vigna:
> Thanks for your backtraces (and patience). Would it be possible for you to
> apply the attached patch to an updated cvs version and see if that fixes the
> problem for you?
Thank you for the patch. Unfortunately it did not avoid the crash. Would
Claus Hindsgaul <[EMAIL PROTECTED]> writes:
| man, 2002-04-29 kl. 15:42 skrev Juergen Vigna:
>> Thanks for your backtraces (and patience). Would it be possible for you to
>> apply the attached patch to an updated cvs version and see if that fixes the
>> problem for you?
>
| Thank you for the
By request, I have obtained the following backtraces from valgrind
(attached) and gdb from a LyX 1.2.0CVS of today with Juergens patch
applied compiled with --disable-optimization. They were both made doing
the same thing as in my prior backtraces.
Claus Hindsgaul
gdb:
(gdb) run
Starting
On Thu, Apr 25, 2002 at 12:13:06AM +0200, Claus Hindsgaul wrote:
Or perhaps an optimized executable...
Still a valgrind bug ! Or binutils, or gcc ... anyway
I have recompiled LyX without optimizations, deleting all -O options
in the configure file (since 'configure --disable-optimizations'
On Thu, Apr 25, 2002 at 12:13:06AM +0200, Claus Hindsgaul wrote:
> Or perhaps an optimized executable...
Still a valgrind bug ! Or binutils, or gcc ... anyway
> I have recompiled LyX without optimizations, deleting all "-O" options
> in the configure file (since 'configure
tir, 2002-04-23 kl. 14:10 skrev Juergen Vigna:
Sorry again what version of LyX are you using? Are you using the current
cvs tree? I seem to see differences in the backtraces valgrind gives and
the sourcecode (for example there is no row-previous() in draw!).
I have now deleted and checked out
On Wed, Apr 24, 2002 at 03:22:18PM +0200, Claus Hindsgaul wrote:
I have now deleted and checked out lyx-devel again from the CVS of
today, rebuilt and produced a new lyxlog.txt the same way (yes, the bug
is still there). The version of valgrind is printed in the header of the
log-file.
On Wednesday 24 April 2002 2:22 pm, Claus Hindsgaul wrote:
tir, 2002-04-23 kl. 14:10 skrev Juergen Vigna:
Sorry again what version of LyX are you using? Are you using the current
cvs tree? I seem to see differences in the backtraces valgrind gives and
the sourcecode (for example there is
ons, 2002-04-24 kl. 15:27 skrev John Levon:
Did that help?
No ! Look at the backtrace yourself then look at the source they are
completely different. Perhaps a valgrind bug ?
Or perhaps an optimized executable...
I have recompiled LyX without optimizations, deleting all -O options
in the
tir, 2002-04-23 kl. 14:10 skrev Juergen Vigna:
> Sorry again what version of LyX are you using? Are you using the current
> cvs tree? I seem to see differences in the backtraces valgrind gives and
> the sourcecode (for example there is no row->previous() in draw!).
I have now deleted and checked
On Wed, Apr 24, 2002 at 03:22:18PM +0200, Claus Hindsgaul wrote:
> I have now deleted and checked out lyx-devel again from the CVS of
> today, rebuilt and produced a new lyxlog.txt the same way (yes, the bug
> is still there). The version of valgrind is printed in the header of the
> log-file.
>
On Wednesday 24 April 2002 2:22 pm, Claus Hindsgaul wrote:
> tir, 2002-04-23 kl. 14:10 skrev Juergen Vigna:
> > Sorry again what version of LyX are you using? Are you using the current
> > cvs tree? I seem to see differences in the backtraces valgrind gives and
> > the sourcecode (for example
ons, 2002-04-24 kl. 15:27 skrev John Levon:
> > Did that help?
>
> No ! Look at the backtrace yourself then look at the source they are
> completely different. Perhaps a valgrind bug ?
Or perhaps an optimized executable...
I have recompiled LyX without optimizations, deleting all "-O" options
Claus == Claus Hindsgaul [EMAIL PROTECTED] writes:
Claus Hi again, With a little help from Jean-Marc I have produced the
Claus following output from gdb while triggering the described crash.
Claus I hope it may help you nail it down.
I have to admit I do not see what happens. Especially the
tir, 2002-04-23 kl. 11:18 skrev Jean-Marc Lasgouttes:
If you have time, you may want to try our valgrind
http://developer.kde.org/~sewardj/
I tried it by simply invoking 'valgrind lyx'. The crash did NOT happen
within valgrind, but a lot of messages were output at the expected time
of the
Does someone of you have some experience with valgring?
==30304== Invalid read of size 4
==30304==at 0x8139486: Row::previous(void) const (lyxrow.C:112)
==30304==by 0x816E337: LyXText::draw(LyXText::DrawRowParams , int ) (text.C:650)
==30304==by 0x8179678:
On Tue, Apr 23, 2002 at 01:02:57PM +0200, Juergen Vigna wrote:
Does someone of you have some experience with valgring?
==30304== Invalid read of size 4
==30304==at 0x8139486: Row::previous(void) const (lyxrow.C:112)
Where is this invalid read in the first listed function or in one of
On 23-Apr-2002 Claus Hindsgaul wrote:
tir, 2002-04-23 kl. 11:18 skrev Jean-Marc Lasgouttes:
If you have time, you may want to try our valgrind
http://developer.kde.org/~sewardj/
I tried it by simply invoking 'valgrind lyx'. The crash did NOT happen
Sorry again what version of LyX are
tir, 2002-04-23 kl. 14:10 skrev Juergen Vigna:
Sorry again what version of LyX are you using? Are you using the current
cvs tree? I seem to see differences in the backtraces valgrind gives and
the sourcecode (for example there is no row-previous() in draw!).
Well it was built from CVS
On 23-Apr-2002 Claus Hindsgaul wrote:
tir, 2002-04-23 kl. 14:10 skrev Juergen Vigna:
Sorry again what version of LyX are you using? Are you using the current
cvs tree? I seem to see differences in the backtraces valgrind gives and
the sourcecode (for example there is no row-previous() in
On Tue, Apr 23, 2002 at 04:33:36PM +0200, Juergen Vigna wrote:
==4426== Invalid read of size 4
==4426==at 0x8139496: Row::previous(void) const (lyxrow.C:112)
==4426==by 0x816E317: LyXText::draw(LyXText::DrawRowParams , int ) (text.C:650)
==4426==by 0x8179658:
> "Claus" == Claus Hindsgaul <[EMAIL PROTECTED]> writes:
Claus> Hi again, With a little help from Jean-Marc I have produced the
Claus> following output from gdb while triggering the described crash.
Claus> I hope it may help you nail it down.
I have to admit I do not see what happens.
tir, 2002-04-23 kl. 11:18 skrev Jean-Marc Lasgouttes:
> If you have time, you may want to try our valgrind
> http://developer.kde.org/~sewardj/
I tried it by simply invoking 'valgrind lyx'. The crash did NOT happen
within valgrind, but a lot of messages were output at the expected time
of the
Does someone of you have some experience with valgring?
==30304== Invalid read of size 4
==30304==at 0x8139486: Row::previous(void) const (lyxrow.C:112)
==30304==by 0x816E337: LyXText::draw(LyXText::DrawRowParams &, int &) (text.C:650)
==30304==by 0x8179678:
On Tue, Apr 23, 2002 at 01:02:57PM +0200, Juergen Vigna wrote:
> Does someone of you have some experience with valgring?
>
> ==30304== Invalid read of size 4
> ==30304==at 0x8139486: Row::previous(void) const (lyxrow.C:112)
>
> Where is this invalid read in the first listed function or in
On 23-Apr-2002 Claus Hindsgaul wrote:
> tir, 2002-04-23 kl. 11:18 skrev Jean-Marc Lasgouttes:
>> If you have time, you may want to try our valgrind
>> http://developer.kde.org/~sewardj/
>
> I tried it by simply invoking 'valgrind lyx'. The crash did NOT happen
Sorry again what version of LyX
tir, 2002-04-23 kl. 14:10 skrev Juergen Vigna:
> Sorry again what version of LyX are you using? Are you using the current
> cvs tree? I seem to see differences in the backtraces valgrind gives and
> the sourcecode (for example there is no row->previous() in draw!).
Well it was built from CVS
On 23-Apr-2002 Claus Hindsgaul wrote:
> tir, 2002-04-23 kl. 14:10 skrev Juergen Vigna:
>> Sorry again what version of LyX are you using? Are you using the current
>> cvs tree? I seem to see differences in the backtraces valgrind gives and
>> the sourcecode (for example there is no
On Tue, Apr 23, 2002 at 04:33:36PM +0200, Juergen Vigna wrote:
> ==4426== Invalid read of size 4
> ==4426==at 0x8139496: Row::previous(void) const (lyxrow.C:112)
> ==4426==by 0x816E317: LyXText::draw(LyXText::DrawRowParams &, int &) (text.C:650)
> ==4426==by 0x8179658:
John == John Levon [EMAIL PROTECTED] writes:
John On Thu, Apr 18, 2002 at 04:23:00PM +0200, Claus Hindsgaul wrote:
2) Use a locale != da_DK. (E.g. C, no_NO, de_AT works)
John I can't reproduce a problem myself. Can you try the open source
John xforms perhaps ?
Or try to run it under gdb and
Hi again,
With a little help from Jean-Marc I have produced the following output
from gdb while triggering the described crash.
I hope it may help you nail it down.
Claus
(gdb) run
Starting program: /usr/local/bin/lyx
Program received signal SIGSEGV, Segmentation fault.
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> On Thu, Apr 18, 2002 at 04:23:00PM +0200, Claus Hindsgaul wrote:
>> 2) Use a locale != da_DK. (E.g. C, no_NO, de_AT works)
John> I can't reproduce a problem myself. Can you try the open source
John> xforms perhaps ?
Or try to run it
Hi again,
With a little help from Jean-Marc I have produced the following output
from gdb while triggering the described crash.
I hope it may help you nail it down.
Claus
(gdb) run
Starting program: /usr/local/bin/lyx
Program received signal SIGSEGV, Segmentation fault.
Hi,
Using the current Danish LyX 1.2.0, I have noticed a strange crash while
opening a couple of similar documents.
LyX catches a SIGSEGV signal without further notice while opening the
documents.
The crash is avioded if:
1) I activate Rescale bitmap fonts in preferences before opening
On Thu, Apr 18, 2002 at 04:23:00PM +0200, Claus Hindsgaul wrote:
2) Use a locale != da_DK. (E.g. C, no_NO, de_AT works)
I can't reproduce a problem myself. Can you try the open source xforms
perhaps ?
regards
john
--
They didn't know what the symbols and paradoxes meant. Instead of
Hi,
Using the current Danish LyX 1.2.0, I have noticed a strange crash while
opening a couple of similar documents.
LyX catches a SIGSEGV signal without further notice while opening the
documents.
The crash is avioded if:
1) I activate "Rescale bitmap fonts" in preferences before opening
On Thu, Apr 18, 2002 at 04:23:00PM +0200, Claus Hindsgaul wrote:
> 2) Use a locale != da_DK. (E.g. C, no_NO, de_AT works)
I can't reproduce a problem myself. Can you try the open source xforms
perhaps ?
regards
john
--
"They didn't know what the symbols and paradoxes meant. Instead of
54 matches
Mail list logo
