Rob,

On Mon, 2002-12-02 at 14:06, Rob Lahaye wrote:
> Darren Freeman wrote:
> > 
> > Play with it, I think I'm right =)
> 
> Yes, you are. I apologize for causing confusion.
> 
> Though I would suggest not to place the lyxdbg script in src/lyx, but
> elsewhere. src/ has the source code; the script should be somewhere else.
> Maybe in the lyx-devel root directory? In that case you may want

makes sense

> `dirname $0`/src/lyx in the for-loop. But as long as the script is not
> (yet) accepted into CVS, this is not an important issue.

In my case I have an alias to lyx that overrides my 1.2.1 install so
it's easy to realias it. But for testing purposes, I've run it from a
link in the CVS build dir (and to encourage it getting into CVS =) )

> > You do seem to assume that I cd to the lyd directory tree before running
> > the script. But the way I've been using it, I cd to where my documents
> > are before running lyxdbg.
> 
> Yes, I assumed that, because that's how I use the CVS build. Anyway, your
> use is also legitimate and using dirname above should solve that problem.

OK well then it's going into 1.4 alongside the other choices already
there.. Maybe it can be 1st choice, with the others as last resort for
more weird cases.

> Cheers,
> Rob.
> 
> PS: wonder if someone else has noticed the charm of your script!?!

or our script =)

Doubt it - nobody else seems to be replying. I suppose they will cotton
on when the next segfault appears and somebody has to use it in a hurry
=)

One other thing - an earlier version included the output of lyx
--version in the trace, which provided a lot of useful info. Shouldn't
it go back? Esp. now that zipping is included.

With the asynchronous lyx and gdb execution, we get lots of info as gdb
looks through your libraries.. I suppose that's helpful too.

The more we cram into the trace the better, since you only ever email a
file into the list when something nasty is happening. The chances are
that many users don't even know what version of GCC they have =)

Have fun,
Darren

Reply via email to