Unassigned buffer_ member in Inset::dispatch()

[Scott Kostyshak]

On Mon, Oct 10, 2022 at 12:36:42PM -0400, Scott Kostyshak wrote:
> On Mon, Oct 10, 2022 at 05:24:50PM +0200, Jean-Marc Lasgouttes wrote:
> > Le 10/10/2022 à 06:29, Scott Kostyshak a écrit :
> > > I noticed the following terminal message:
> > > 
> > >    Unassigned buffer_ member in Inset::dispatch()
> > >    LyX Code: 78 name: mathnest
> > > 
> > > Unfortunately, I could not reproduce it. Does just knowing the name,
> > > "mathnest", provide a clue, or we would need a backtrace? If so, should
> > > we add an assert here?
> > 
> > It is a bit difficult to trace this. Note however that a good way to see
> > those unassigned buffer_ members is to toggle devel-mode on. Then all these
> > insets will have a red background.
> 
> I had no idea bout devel-mode. I will use it and try to come up with a
> recipe to reproduce. I've seen the terminal message before, but only
> once every few months or so, so it might take me some time.

After a long editing session and quitting LyX, I noticed the following messages:

Unassigned buffer_ member in Inset::dispatch()
LyX Code: 85 name: mathscript
Unassigned buffer_ member in Inset::dispatch()
LyX Code: 61 name: mathdelim

I didn't have devel mode on.

Would it make sense to add an assert? That will be helpful to figure out
how to reproduce. I can add it locally, but is there a reason we don't
have it added in the code? i.e., see attached patch.

Scott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Add-assert.patch
Type: text/x-diff
Size: 851 bytes
Desc: not available
URL: <http://lists.lyx.org/pipermail/lyx-devel/attachments/20230113/361505a0/attachment.patch>