On Fri, Apr 21, 2017 at 09:08:36AM +0200, Kornel Benko wrote:
> Am Donnerstag, 20. April 2017 um 23:48:12, schrieb Scott Kostyshak
>
> > On Thu, Apr 20, 2017 at 07:59:05PM +0200, Kornel Benko wrote:
> > > Am Donnerstag, 20. April 2017 um 13:02:32, schrieb Scott Kostyshak
> > >
Am Freitag, 21. April 2017 um 00:47:38, schrieb Scott Kostyshak
> On Thu, Apr 20, 2017 at 11:48:12PM -0400, Scott Kostyshak wrote:
>
> > > $1 = (const lyx::support::FileName &) @0x3559560: {
> > > _vptr.FileName = 0x38ca7d0,
> > > d = 0x0
> > > }
> >
> > What information
Am Donnerstag, 20. April 2017 um 23:48:12, schrieb Scott Kostyshak
> On Thu, Apr 20, 2017 at 07:59:05PM +0200, Kornel Benko wrote:
> > Am Donnerstag, 20. April 2017 um 13:02:32, schrieb Scott Kostyshak
> >
> > > On Thu, Apr 20, 2017 at 04:21:49AM -0400,
On Thu, Apr 20, 2017 at 11:48:12PM -0400, Scott Kostyshak wrote:
> > $1 = (const lyx::support::FileName &) @0x3559560: {
> > _vptr.FileName = 0x38ca7d0,
> > d = 0x0
> > }
>
> What information does this tell you? I guess that 0x38ca7d0 is a memory
> address of the pointer?
Ah so the idea is
On Thu, Apr 20, 2017 at 07:59:05PM +0200, Kornel Benko wrote:
> Am Donnerstag, 20. April 2017 um 13:02:32, schrieb Scott Kostyshak
>
> > On Thu, Apr 20, 2017 at 04:21:49AM -0400, Scott Kostyshak wrote:
> > > On Thu, Apr 20, 2017 at 09:10:54AM +0200, Tommaso Cucinotta wrote:
> >
On 20/04/2017 22:28, Guillaume MM wrote:
The attached fixes it for me.
for me as well, pushed, thanx :-)!
T.
Le 20/04/2017 à 19:02, Scott Kostyshak a écrit :
On Thu, Apr 20, 2017 at 04:21:49AM -0400, Scott Kostyshak wrote:
On Thu, Apr 20, 2017 at 09:10:54AM +0200, Tommaso Cucinotta wrote:
A 2nd SIGSEGV, involving similar actions, but the crash happens earlier, so
I guess it's a different bug:
1.
Am Donnerstag, 20. April 2017 um 13:02:32, schrieb Scott Kostyshak
> On Thu, Apr 20, 2017 at 04:21:49AM -0400, Scott Kostyshak wrote:
> > On Thu, Apr 20, 2017 at 09:10:54AM +0200, Tommaso Cucinotta wrote:
> > > A 2nd SIGSEGV, involving similar actions, but the crash happens
On 20/04/2017 19:02, Scott Kostyshak wrote:
My bisect lead to 244de5d2 but I'm not confident in the bisect (for some
revisions I could reproduce once and then not a separate time. I always
cleared the cache each time but still had mixed results).
When git bisect narrowed in on the commits
On Thu, Apr 20, 2017 at 04:21:49AM -0400, Scott Kostyshak wrote:
> On Thu, Apr 20, 2017 at 09:10:54AM +0200, Tommaso Cucinotta wrote:
> > A 2nd SIGSEGV, involving similar actions, but the crash happens earlier, so
> > I guess it's a different bug:
> > 1. clear your ~/.lyx-trunk/cache/*
> > 2.
On Thu, Apr 20, 2017 at 09:10:54AM +0200, Tommaso Cucinotta wrote:
> A 2nd SIGSEGV, involving similar actions, but the crash happens earlier, so
> I guess it's a different bug:
> 1. clear your ~/.lyx-trunk/cache/*
> 2. start LyX, new doc
> 3. type "info-insert icon whatevernonsense"
>
> => LyX
A 2nd SIGSEGV, involving similar actions, but the crash happens earlier, so
I guess it's a different bug:
1. clear your ~/.lyx-trunk/cache/*
2. start LyX, new doc
3. type "info-insert icon whatevernonsense"
=> LyX SIGNAL CAUGHT dialog with std::bad_alloc.
T.
On 20/04/2017 09:03,
Hi,
I'm seeing a SIGSEGV in the bug-export-latex-in.txt autotest [1].
Albeit the test doesn't fail, I'm clearly seeing on screen that LyX is showing
the SIGSEGV dialog. Trying a manual repro, it doesn't seem to happen, but
running it in the autotests it does happen all the times.
Anyone might
13 matches
Mail list logo