On Fri, Feb 05, 1999 at 02:28:41PM +0100, Lars Gullik Bjønnes wrote:
> >> Allan Rae writes:
>
> AR> AFA memcpy is concerned I found it necessary to use such
> AR> "low-level" techniques to squeeze enough performance out of a
> AR> couple of very heavily utilized LString methods so they
>
>> Allan Rae writes:
AR> AFA memcpy is concerned I found it necessary to use such
AR> "low-level" techniques to squeeze enough performance out of a
AR> couple of very heavily utilized LString methods so they
AR> resulting in significant performance improvements. As a result
Low-level i
On 4 Feb 1999, Lars Gullik Bjønnes wrote:
> *Andre' Poenitz writes:
> | I once was at a point to have a closer look at the LyX sources and
> | I really wondered why there are all these funny pointers and direct
> | memory access operations in it. Using *real* C++ (not 'C with
> | classes') sh
On Don, 04 Feb 1999 Alejandro Aguilar Sierra wrote:
>If you're talking about the message of January 27, yes I have it, but you
>say at the end:
>
>> My change actually doesn't help the crash :-(
>
>I think the problem is something else. I'll check it out tomorrow.
No, I think that is not the mes
On Thu, 4 Feb 1999, Jochen Kuepper wrote:
> Alejandro,
> as I send in before 1.0.0 - do you think these memcpies are save
> ( Regarding memory representation ) ? What's about assignments + casts ?
Yes, it has worked reasonably well during 3 years. Fred had answered
this question better than I wa
*Andre' Poenitz writes:
| I once was at a point to have a closer look at the LyX sources and
| I really wondered why there are all these funny pointers and direct
| memory access operations in it. Using *real* C++ (not 'C with
| classes') should make all but a few low level operations
| unnec
On Don, 04 Feb 1999 Fred Hucht wrote:
[Teach some C]
>OK?
Well, fine :-)
Greetings,
Jochen
---
Jochen K"upper
Heinrich-Heine-Universit"at D"usseldorf [EMAIL PROTECTED]
Institut f"ur Physikalische Chemie I
Universit"
On Thu, 4 Feb 1999, Jochen Kuepper wrote:
[Diskussion about the combo:]
MathedInset* p;
memcpy(&p, &array->bf[pos+1], sizeof(p));
memcpy(&array->bf[pos+1], &p, sizeof(p));
JK> Well, if its not on the correct boundary and you access *pointer
JK> later on, it will crash !
No. Think about it.
Concerning the memcpy: I don't really see the need for such low-level
stuff in that place. Even if it is safe, nobody can check it by a
glance. I think it is *much* wiser to trust the compiler to put in the
right code in and use 'higher level' operation (such as assignments of
whole objects etc).
On Don, 04 Feb 1999 Fred Hucht wrote:
>On Thu, 4 Feb 1999, Jochen Kuepper wrote:
>
>JK> On Don, 04 Feb 1999 Alejandro Aguilar Sierra wrote:
>JK>
>JK> >In GetInset we do:
>JK> >
>JK> > MathedInset* p;
>JK> > memcpy(&p, &array->bf[pos+1], sizeof(p));
>JK> >
>JK> >and in the function to insert in
On Thu, 4 Feb 1999, Jochen Kuepper wrote:
JK> On Don, 04 Feb 1999 Alejandro Aguilar Sierra wrote:
JK>
JK> >In GetInset we do:
JK> >
JK> > MathedInset* p;
JK> > memcpy(&p, &array->bf[pos+1], sizeof(p));
JK> >
JK> >and in the function to insert insets we do (same type of p) :
JK> >
JK> > me
On Don, 04 Feb 1999 Alejandro Aguilar Sierra wrote:
>In GetInset we do:
>
> MathedInset* p;
> memcpy(&p, &array->bf[pos+1], sizeof(p));
>
>and in the function to insert insets we do (same type of p) :
>
> memcpy(&array->bf[pos+1], &p, sizeof(p));
>
>so it's consistent, hmm.. ha
On Don, 04 Feb 1999 Bob McElrath wrote:
>On Wed, 3 Feb 1999, Alejandro Aguilar Sierra wrote:
>
>> On Wed, 3 Feb 1999, Bob McElrath wrote:
>>
>> > Hmmm...likely an alpha-specific problem then. I'm using egcs 1.1.1 on an
>> > alpha LX164, 533MHz (compiled lyx myself...not from RPM or deb). Know o
On Don, 04 Feb 1999 Garst R. Reese wrote:
>Bob McElrath wrote:
>>
>> Lyx 1.0.0 (and all pre versions that I've tried) crash when I try to load
>> some documents created with 0.12. Here's the backtrace:
>
>> Attached is the document that caused this crash. This is on a:
>> (0) uname -a
>> Linux
On Wed, 3 Feb 1999, Alejandro Aguilar Sierra wrote:
> On Wed, 3 Feb 1999, Bob McElrath wrote:
>
> > Hmmm...likely an alpha-specific problem then. I'm using egcs 1.1.1 on an
> > alpha LX164, 533MHz (compiled lyx myself...not from RPM or deb). Know of
> > anywhere in your math code that you ass
On Wed, 3 Feb 1999, Bob McElrath wrote:
> Hmmm...likely an alpha-specific problem then. I'm using egcs 1.1.1 on an
> alpha LX164, 533MHz (compiled lyx myself...not from RPM or deb). Know of
> anywhere in your math code that you assume
> sizeof(long) == sizeof(int) == sizeof(void*)? Because it
On Thu, 4 Feb 1999, Garst R. Reese wrote:
> Bob McElrath wrote:
> >
> > Lyx 1.0.0 (and all pre versions that I've tried) crash when I try to load
> > some documents created with 0.12. Here's the backtrace:
>
> > Attached is the document that caused this crash. This is on a:
> > (0) uname -a
Mate Wierdl wrote:
>
> Well his machine is not intel.
Hey, I can read too. Just trying to narrow the problem a bit.
Well his machine is not intel.
Mate
Bob McElrath wrote:
>
> Lyx 1.0.0 (and all pre versions that I've tried) crash when I try to load
> some documents created with 0.12. Here's the backtrace:
> Attached is the document that caused this crash. This is on a:
> (0) uname
Bob McElrath wrote:
>
> Lyx 1.0.0 (and all pre versions that I've tried) crash when I try to load
> some documents created with 0.12. Here's the backtrace:
> Attached is the document that caused this crash. This is on a:
> (0) uname -a
> Linux draal.physics.wisc.edu 2.2.1-ac1 #18 Wed Feb 3 11
Lyx 1.0.0 (and all pre versions that I've tried) crash when I try to load
some documents created with 0.12. Here's the backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x1200fa5b4 in MathParInset::Metrics (this=0x12039f7b0) at math_draw.C:172
172 p->SetStyle(size
21 matches
Mail list logo
