--with-pgtk crashes

--with-pgtk crashes

[T.V Raman]

Latest build from head with --with-pgtk now crashes on Linux (Debian)
when started under X.


Taking out the --with-pgtk and rebuilding works fine.



-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

Re: --with-pgtk crashes

[Eli Zaretskii]

> Date: Thu, 06 Jan 2022 10:03:25 -0800
> From: "T.V Raman" <raman@google.com>
> 
> Latest build from head with --with-pgtk now crashes on Linux (Debian)
> when started under X.

Can you post a backtrace from the crash, please?  That will make
finding the culprit much easier and faster.

Thanks.

Re: --with-pgtk crashes

[T.V Raman]

It doesn't yield a backtrace -- even if started with --dbug-init ---
basically emacs launches, then the window disappears -- it dumps some
debug addresses in .xsession-errors but they dont look meaningful.
Eli Zaretskii writes:
 > > Date: Thu, 06 Jan 2022 10:03:25 -0800
 > > From: "T.V Raman" <raman@google.com>
 > > 
 > > Latest build from head with --with-pgtk now crashes on Linux (Debian)
 > > when started under X.
 > 
 > Can you post a backtrace from the crash, please?  That will make
 > finding the culprit much easier and faster.
 > 
 > Thanks.

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

--

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

Re: --with-pgtk crashes

[Po Lu]

"T.V Raman" <raman@google.com> writes:

> It doesn't yield a backtrace -- even if started with --dbug-init ---
> basically emacs launches, then the window disappears -- it dumps some
> debug addresses in .xsession-errors but they dont look meaningful.

Please run Emacs under GDB, and show a backtrace from that.

Thanks.

Re: --with-pgtk crashes

[Tassilo Horn]

Po Lu <luangruo@yahoo.com> writes:

>> It doesn't yield a backtrace -- even if started with --dbug-init ---
>> basically emacs launches, then the window disappears -- it dumps some
>> debug addresses in .xsession-errors but they dont look meaningful.
>
> Please run Emacs under GDB, and show a backtrace from that.

FWIW, I'm on wayland with PGTK enabled and it's working just fine.  When
I explicitly state that it should run unter xwayland instead using

  env -u WAYLAND_DISPLAY emacs -Q

I get no crash but except for the mode-line and menu-bar nothing is
displayed/rendered, that is, the scratch buffer is and stays empty and
so is the echo area.  There's also no tool-bar.  I can see that emacs
reacts, e.g., `C-h i' will open info which I can see because the frame
changes its title.

Oh, well, when I resize the emacs frame a bit (I'm using a tiling
compositior), out of sudden all those missing things appear. :-)
So I guess that's a separate issue.  I'll submit a bug report later.

Bye,
Tassilo

Re: --with-pgtk crashes

[Po Lu]

Tassilo Horn <tsdh@gnu.org> writes:

> Po Lu <luangruo@yahoo.com> writes:
>
>>> It doesn't yield a backtrace -- even if started with --dbug-init ---
>>> basically emacs launches, then the window disappears -- it dumps some
>>> debug addresses in .xsession-errors but they dont look meaningful.
>>
>> Please run Emacs under GDB, and show a backtrace from that.
>
> FWIW, I'm on wayland with PGTK enabled and it's working just fine.  When
> I explicitly state that it should run unter xwayland instead using
>
>   env -u WAYLAND_DISPLAY emacs -Q
>
> I get no crash but except for the mode-line and menu-bar nothing is
> displayed/rendered, that is, the scratch buffer is and stays empty and
> so is the echo area.  There's also no tool-bar.  I can see that emacs
> reacts, e.g., `C-h i' will open info which I can see because the frame
> changes its title.
>
> Oh, well, when I resize the emacs frame a bit (I'm using a tiling
> compositior), out of sudden all those missing things appear. :-)
> So I guess that's a separate issue.  I'll submit a bug report later.

Thanks, one question though: does this happen with other GTK programs
running inside Xwayland?

Re: --with-pgtk crashes

[Tassilo Horn]

Po Lu <luangruo@yahoo.com> writes:

>> I get no crash but except for the mode-line and menu-bar nothing is
>> displayed/rendered, that is, the scratch buffer is and stays empty
>> and so is the echo area.  There's also no tool-bar.  I can see that
>> emacs reacts, e.g., `C-h i' will open info which I can see because
>> the frame changes its title.
>>
>> Oh, well, when I resize the emacs frame a bit (I'm using a tiling
>> compositior), out of sudden all those missing things appear. :-) So I
>> guess that's a separate issue.  I'll submit a bug report later.
>
> Thanks, one question though: does this happen with other GTK programs
> running inside Xwayland?

No, I've tried gedit (40.1), gimp (2.10.30), and firefox (96.0b10).
They all worked properly except firefox was light-themed although it's
usually dark-themed here.

Bye,
Tassilo

Re: --with-pgtk crashes

[T.V Raman]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 260 bytes --]


If it helps, a build from Tuesday did not crash, the build from
yesterday's git update crashed, so you might well be able to pin it down
by bisecting

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8

Re: --with-pgtk crashes

[Eli Zaretskii]

> From: Po Lu <luangruo@yahoo.com>
> Cc: eliz@gnu.org,  emacs-devel@gnu.org
> Date: Fri, 07 Jan 2022 08:43:55 +0800
> 
> "T.V Raman" <raman@google.com> writes:
> 
> > It doesn't yield a backtrace -- even if started with --dbug-init ---
> > basically emacs launches, then the window disappears -- it dumps some
> > debug addresses in .xsession-errors but they dont look meaningful.
> 
> Please run Emacs under GDB, and show a backtrace from that.

Yes, that's what I meant (a backtrace from a crash is only interesting
on the C level).  Sorry for being unclear.

Re: --with-pgtk crashes

[T.V Raman]

sorry, I ant do that, I'll let someone else in the emacs-devel
community help.Po Lu writes:
 > "T.V Raman" <raman@google.com> writes:
 > 
 > > It doesn't yield a backtrace -- even if started with --dbug-init ---
 > > basically emacs launches, then the window disappears -- it dumps some
 > > debug addresses in .xsession-errors but they dont look meaningful.
 > 
 > Please run Emacs under GDB, and show a backtrace from that.
 > 
 > Thanks.

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

--

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮