unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* C-g crash
@ 2006-07-23  5:27 Richard Stallman
  2006-07-23  9:05 ` Andreas Schwab
  0 siblings, 1 reply; 5+ messages in thread
From: Richard Stallman @ 2006-07-23  5:27 UTC (permalink / raw)


The backtrace after the crash showed one stack frame
calling __kernel_vsyscall.

Does anyone know what that does?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: C-g crash
  2006-07-23  5:27 C-g crash Richard Stallman
@ 2006-07-23  9:05 ` Andreas Schwab
  2006-07-23 17:34   ` Richard Stallman
  0 siblings, 1 reply; 5+ messages in thread
From: Andreas Schwab @ 2006-07-23  9:05 UTC (permalink / raw)
  Cc: emacs-devel

Richard Stallman <rms@gnu.org> writes:

> The backtrace after the crash showed one stack frame
> calling __kernel_vsyscall.
>
> Does anyone know what that does?

It's the syscall trampoline provided by the kernel.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: C-g crash
  2006-07-23  9:05 ` Andreas Schwab
@ 2006-07-23 17:34   ` Richard Stallman
  2006-07-23 19:00     ` Andreas Schwab
  0 siblings, 1 reply; 5+ messages in thread
From: Richard Stallman @ 2006-07-23 17:34 UTC (permalink / raw)
  Cc: emacs-devel

    It's the syscall trampoline provided by the kernel.

Could you explain more precisely?

Until very recently, I never saw Emacs stopped in __kernel_vsyscall.
Is it something fairly new?

Is there a way to determine which system call it is
by looking at some of the registers?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: C-g crash
  2006-07-23 17:34   ` Richard Stallman
@ 2006-07-23 19:00     ` Andreas Schwab
  2006-07-24 14:42       ` Richard Stallman
  0 siblings, 1 reply; 5+ messages in thread
From: Andreas Schwab @ 2006-07-23 19:00 UTC (permalink / raw)
  Cc: emacs-devel

Richard Stallman <rms@gnu.org> writes:

>     It's the syscall trampoline provided by the kernel.
>
> Could you explain more precisely?

It's also known as vDSO.  That's pretty much all I know about it.

> Is there a way to determine which system call it is
> by looking at some of the registers?

It also contains the signal trampoline, so you may just be looking at a
signal frame.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: C-g crash
  2006-07-23 19:00     ` Andreas Schwab
@ 2006-07-24 14:42       ` Richard Stallman
  0 siblings, 0 replies; 5+ messages in thread
From: Richard Stallman @ 2006-07-24 14:42 UTC (permalink / raw)
  Cc: emacs-devel

    > Is there a way to determine which system call it is
    > by looking at some of the registers?

    It also contains the signal trampoline, so you may just be looking at a
    signal frame.

If someone can tell me how to diagnose this, I would appreciate it.

I have started editing using the souces as of 2006-07-10.
We will see if it crashes.  I have a suspicion that the sit-for
change is somehow responsible, but that is not yet proved.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2006-07-24 14:42 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-23  5:27 C-g crash Richard Stallman
2006-07-23  9:05 ` Andreas Schwab
2006-07-23 17:34   ` Richard Stallman
2006-07-23 19:00     ` Andreas Schwab
2006-07-24 14:42       ` Richard Stallman

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).