From: Eli Zaretskii <eliz@gnu.org>
To: dmalcolm@redhat.com
Cc: akrl@sdf.org, andrewjmoreton@gmail.com, 46495@debbugs.gnu.org
Subject: bug#46495: 28.0.50; [native-comp] Build fails for 32bit --with-wide-int
Date: Tue, 30 Mar 2021 12:06:38 +0300 [thread overview]
Message-ID: <834kgtko2p.fsf@gnu.org> (raw)
In-Reply-To: <837dlpkrma.fsf@gnu.org> (message from Eli Zaretskii on Tue, 30 Mar 2021 10:50:05 +0300)
> Date: Tue, 30 Mar 2021 10:50:05 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: andrewjmoreton@gmail.com, dmalcolm@redhat.com, 46495@debbugs.gnu.org
>
> Here's what I did:
>
> . compiled the example with -gdwarf-4 -g3
> . started GDB and ran the program until it calls the 'greet'
> function
> . used "si" and "ni" commands to step into 'greet' and through the
> functions it calls
I have now compiled a slightly modified version of the hello world
example, after adding this to the source:
gcc_jit_context_set_bool_option (
ctxt,
GCC_JIT_BOOL_OPTION_DEBUGINFO,
1);
The results under debugger are slightly better, for example, the
arguments to JIT functions are shown:
(gdb) bt
#0 0x6ac81280 in greet (name=0x406088 "world")
from C:\DOCUME~1\Zaretzky\LOCALS~1\Temp\libgccjit-0z6iua\fake.so
However, the "??" thingies and the incomplete backtraces are still
present, here are two examples:
#0 0x77c418ab in printf () from C:\WINDOWS\system32\msvcrt.dll
#1 0x00000001 in ?? ()
#2 0x77c5fca0 in msvcrt!_iob () from C:\WINDOWS\system32\msvcrt.dll
#3 0x77c5fca0 in msvcrt!_iob () from C:\WINDOWS\system32\msvcrt.dll
#4 0x6ac83044 in ?? ()
from C:\DOCUME~1\Zaretzky\LOCALS~1\Temp\libgccjit-0z6iua\fake.so
#5 0x6ac81299 in greet (name=0x406088 "world")
from C:\DOCUME~1\Zaretzky\LOCALS~1\Temp\libgccjit-0z6iua\fake.so
#6 0x004016f5 in main (argc=1, argv=0x3e2978) at tut01d-hello-world.c:121
#0 0x77c41883 in printf () from C:\WINDOWS\system32\msvcrt.dll
#1 0x00000001 in ?? ()
#2 0x77c5fca0 in msvcrt!_iob () from C:\WINDOWS\system32\msvcrt.dll
#3 0x00000000 in ?? ()
This is quite disappointing. It probably means that debugging Emacs
with natively-compiled Lisp will be much harder on MS-Windows, if you
happen to be in a situation (whose causes are still unclear to me,
probably some minor variations of the prologue code?) with these
incomplete backtraces.
I also have 3 followup questions:
1) When GCC_JIT_BOOL_OPTION_DEBUGINFO is used, what kind of debug
info is generated by libgccjit? is it DWARF2 or stabs or something
else? Using "objdump -W", it looks like DWARF2, but if so, why
isn't GDB able to produce a decent backtrace?
2) If the debug info created under GCC_JIT_BOOL_OPTION_DEBUGINFO is
not DWARF2, is it possible to use
gcc_jit_context_add_command_line_option to request "-gdwarf-4" or
similar, like we do with the command-line GCC, so that the debug
info for the JIT code is more detailed and accurate?
3) I see in my temporary directory subdirectories, created when I run
the example program, with files fake.s and fake.so. Are they
supposed to be left there, or are they supposed to be deleted
when the program exits?
Thanks.
next prev parent reply other threads:[~2021-03-30 9:06 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 17:57 bug#46495: 28.0.50; [native-comp] Build fails for 32bit --with-wide-int Andy Moreton
2021-02-13 18:10 ` Eli Zaretskii
2021-02-13 20:23 ` Andy Moreton
2021-02-14 15:59 ` Eli Zaretskii
2021-02-14 13:24 ` Andy Moreton
2021-02-14 15:56 ` Eli Zaretskii
2021-02-14 19:26 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-15 9:01 ` Andy Moreton
2021-02-15 10:19 ` Eli Zaretskii
2021-02-15 12:56 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-16 9:34 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-16 15:29 ` Eli Zaretskii
2021-02-16 16:30 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-16 17:01 ` Eli Zaretskii
2021-02-16 17:17 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-16 19:49 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-16 21:51 ` Andy Moreton
2021-02-17 9:04 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-17 18:03 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-18 22:36 ` Andy Moreton
2021-02-19 14:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-19 16:01 ` Andy Moreton
2021-02-19 16:06 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-19 17:01 ` Eli Zaretskii
2021-02-19 17:35 ` Andy Moreton
2021-02-19 19:36 ` Eli Zaretskii
2021-02-19 22:07 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-26 10:18 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-26 11:27 ` Eli Zaretskii
2021-03-26 13:10 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-29 15:55 ` Eli Zaretskii
2021-03-29 16:15 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-29 16:59 ` Eli Zaretskii
2021-03-29 18:11 ` David Malcolm
2021-03-29 20:46 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-30 7:50 ` Eli Zaretskii
2021-03-30 9:06 ` Eli Zaretskii [this message]
2021-03-31 8:13 ` Eli Zaretskii
2021-03-31 13:03 ` David Malcolm
2021-03-31 13:13 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 13:35 ` Eli Zaretskii
2021-03-31 13:33 ` Eli Zaretskii
2021-03-30 9:22 ` Eli Zaretskii
2021-03-30 14:33 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-30 14:37 ` Eli Zaretskii
2021-03-30 19:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 8:07 ` Eli Zaretskii
2021-03-31 8:47 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 11:41 ` Eli Zaretskii
2021-03-31 12:16 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 12:27 ` Eli Zaretskii
2021-03-31 18:26 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 10:01 ` Eli Zaretskii
2021-03-31 10:19 ` Eli Zaretskii
2021-03-31 10:33 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 10:55 ` Eli Zaretskii
2021-03-31 12:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 12:41 ` Eli Zaretskii
2021-03-31 12:53 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 11:10 ` Eli Zaretskii
2021-03-31 12:25 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 12:33 ` Eli Zaretskii
2021-03-31 18:52 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 19:16 ` Eli Zaretskii
2021-03-31 19:22 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 19:35 ` Eli Zaretskii
2021-03-31 19:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 6:37 ` Eli Zaretskii
2021-04-01 7:07 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 7:42 ` Eli Zaretskii
2021-04-01 8:18 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-01 8:43 ` Eli Zaretskii
2021-04-01 14:16 ` Michael Welsh Duggan
2021-04-01 19:52 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-10 16:49 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-10 17:38 ` Eli Zaretskii
2021-03-31 19:40 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-31 10:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834kgtko2p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46495@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=andrewjmoreton@gmail.com \
--cc=dmalcolm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.