Am Thu, 31 Jul 2025 12:36:56 +0200
schrieb Scott Kostyshak <skost...@lyx.org>:

> On Thu, Jul 31, 2025 at 11:44:16AM +0200, Pavel Sanda wrote:
> > On Thu, Jul 31, 2025 at 02:37:06AM +0000, test...@tester.lyx.org wrote:  
> > >   CXX      Trans.o
> > > Trans.cpp: In member function 'const lyx::docstring
> > > lyx::Trans::process(lyx::char_type, lyx::TransManager&)': 
> > > Trans.cpp:365:40: error:
> > > '((const __gnu_cxx::__alloc_traits<std::allocator<wchar_t>,
> > > wchar_t>::value_type*)((char*)&t + offsetof(const std::__cxx11::docstring,
> > > std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>,
> > > std::allocator<wchar_t> >::<unnamed>)))[1]' may be used uninitialized
> > > [-Werror=maybe-uninitialized] 365 |         return k.deadkey(c,
> > > kmod_list_[static_cast<tex_accent>(t[1])]); |
> > >  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Trans.cpp:357:25: note: 't' declared here 
> > > 357 |
> > >    docstring const t = match(c); |                         ^  
> > 
> > 
> > I do not know what the code is supposed to do, but clearly we don't test 
> > for the
> > combination of t.empty() && c = 0
> > .
> > Can such case appear? If so should we return docstring()?
> > 
> > Pavel
> > (Not sure why we are hit by this right now (maybe gcc was updated on the 
> > testing
> > machine)).  
> 
> Indeed strange. I don't see this on my system with the same flag. I have
> GCC version 15.0.1.
> 
> Scott

I tried too, but nothing. Neither with gcc 14.2.0, gcc 13.3.0 nor with clang 
18.1.3

        Kornel

Attachment: pgpjrQgL7t16T.pgp
Description: Digitale Signatur von OpenPGP

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Reply via email to