On Tue, Jun 11, 2024 at 06:09:10PM GMT, Jean-Marc Lasgouttes wrote:
> Le 06/06/2024 à 17:33, Scott Kostyshak a écrit :
> > On Thu, Jun 06, 2024 at 09:00:05AM GMT, Jean-Marc Lasgouttes wrote:
> > > Le 20/05/2024 à 03:45, Scott Kostyshak a écrit :
> > > > Great, thanks! I pulled in the fix, made a
Le 06/06/2024 à 17:33, Scott Kostyshak a écrit :
On Thu, Jun 06, 2024 at 09:00:05AM GMT, Jean-Marc Lasgouttes wrote:
Le 20/05/2024 à 03:45, Scott Kostyshak a écrit :
Great, thanks! I pulled in the fix, made a fresh build and I get another error
along the same lines.
Actually the fix was
On Thu, Jun 06, 2024 at 06:33:35PM GMT, Jean-Marc Lasgouttes wrote:
> Le 06/06/2024 à 17:33, Scott Kostyshak a écrit :
> > On Thu, Jun 06, 2024 at 09:00:05AM GMT, Jean-Marc Lasgouttes wrote:
> > > Le 20/05/2024 à 03:45, Scott Kostyshak a écrit :
> > > > Great, thanks! I pulled in the fix, made a
Le 06/06/2024 à 17:33, Scott Kostyshak a écrit :
On Thu, Jun 06, 2024 at 09:00:05AM GMT, Jean-Marc Lasgouttes wrote:
Le 20/05/2024 à 03:45, Scott Kostyshak a écrit :
Great, thanks! I pulled in the fix, made a fresh build and I get another error
along the same lines.
Actually the fix was
On Thu, Jun 06, 2024 at 09:00:05AM GMT, Jean-Marc Lasgouttes wrote:
> Le 20/05/2024 à 03:45, Scott Kostyshak a écrit :
> > Great, thanks! I pulled in the fix, made a fresh build and I get another
> > error along the same lines.
>
> Actually the fix was faulty. Could you check that the issue is
Le 20/05/2024 à 03:45, Scott Kostyshak a écrit :
Great, thanks! I pulled in the fix, made a fresh build and I get another error
along the same lines.
Actually the fix was faulty. Could you check that the issue is gone now?
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
On Mon, May 20, 2024 at 02:24:12PM GMT, Jean-Marc Lasgouttes wrote:
> Le 20/05/2024 à 03:45, Scott Kostyshak a écrit :
> > Great, thanks! I pulled in the fix, made a fresh build and I get another
> > error along the same lines.
> >
> > Note my version shows I've pulled in Riki's fix:
> >
> >
Le 20/05/2024 à 03:45, Scott Kostyshak a écrit :
Great, thanks! I pulled in the fix, made a fresh build and I get another error
along the same lines.
Note my version shows I've pulled in Riki's fix:
$ lyx --version
LyX 2.5.0~devel (2024-05-20)
Git commit hash 2d86b881
I attach the
This is very weird. It is at the same location AFAICS.
JMarc
Le 20 mai 2024 03:45:23 GMT+02:00, Scott Kostyshak a écrit :
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
pulled in Riki's fix:
$ lyx --version
LyX 2.5.0~devel (2024-05-20)
Git commit hash 2d86b881
I attach the backtrace.
Scott
/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/debug/safe_iterator.h:472:
In function:
bool gnu_debug::operator==(const gnu_debug::_Safe_iterator:
On 5/19/24 15:15, Richard Kimberly Heck wrote:
On 5/19/24 14:49, Jean-Marc Lasgouttes wrote:
Le 19/05/2024 à 20:20, Jean-Marc Lasgouttes a écrit :
If you look at the error details, it seems to me that the addresses
are different. But this is weird.
Note that we can use count() instead of
On 5/19/24 14:49, Jean-Marc Lasgouttes wrote:
Le 19/05/2024 à 20:20, Jean-Marc Lasgouttes a écrit :
If you look at the error details, it seems to me that the addresses
are different. But this is weird.
Note that we can use count() instead of find(), which would solve the
issue.
What about
Le 19/05/2024 à 20:20, Jean-Marc Lasgouttes a écrit :
If you look at the error details, it seems to me that the addresses are
different. But this is weird.
Note that we can use count() instead of find(), which would solve the
issue.
What about that? It seems that the compiler was right
Le 19/05/2024 à 20:11, Richard Kimberly Heck a écrit :
On 5/19/24 13:55, Scott Kostyshak wrote:
On Sun, May 19, 2024 at 07:27:42PM GMT, Jean-Marc Lasgouttes wrote:
Le 18/05/2024 à 17:28, Scott Kostyshak a écrit :
When I compile LyX with some compiler debug flags and extra checks, I
get the
) && runparams.use_hyperref &&
il.latexname() == "url"
&& il.required().find("url") != il.required().end()) {
The error says: "attempt to compare iterators from different sequences."
How is this possible?
Indeed the error message gives two diffe
On 5/19/24 13:55, Scott Kostyshak wrote:
On Sun, May 19, 2024 at 07:27:42PM GMT, Jean-Marc Lasgouttes wrote:
Le 18/05/2024 à 17:28, Scott Kostyshak a écrit :
When I compile LyX with some compiler debug flags and extra checks, I
get the output below when trying to compile a .lyx file to PDF.
nu_debug::operator==(const gnu_debug::_Safe_iterator::_Self &,
const gnu_debug::_Safe_iterator::_Self &)
Error: attempt to compare iterators from different sequences.
Objects involved in the operation:
iterator "lhs" @ 0x7fffc8de8750 {
type = std::_Rb_tree_const_iterato
ag>::_Self&)
Error: attempt to compare iterators from different sequences.
Objects involved in the operation:
iterator "lhs" @ 0x7f60d4fefbc0 {
type = std::_Rb_tree_const_iterator, std::allocator > > (constant iterator);
state = dereferenceable (star
bug::set >, std::forward_iterator_tag>::_Self&, const
_Safe_iterator >, std::debug::set >, std::forward_iterator_tag>::_Self&)
Error: attempt to compare iterators from different sequences.
Objects involved in the operation:
iterator "lhs"
19 matches
Mail list logo
