This list is closed, nobody may subscribe to it.
2014 |
Jan
|
Feb
|
Mar
(6) |
Apr
(57) |
May
(43) |
Jun
(24) |
Jul
(21) |
Aug
(70) |
Sep
(112) |
Oct
(107) |
Nov
(150) |
Dec
(23) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2015 |
Jan
(35) |
Feb
(58) |
Mar
(64) |
Apr
(131) |
May
(71) |
Jun
(31) |
Jul
(29) |
Aug
(30) |
Sep
(22) |
Oct
(13) |
Nov
(46) |
Dec
(22) |
2016 |
Jan
(29) |
Feb
(49) |
Mar
(79) |
Apr
(67) |
May
(14) |
Jun
(5) |
Jul
(40) |
Aug
(31) |
Sep
(23) |
Oct
(34) |
Nov
(38) |
Dec
(28) |
2017 |
Jan
(36) |
Feb
(61) |
Mar
(18) |
Apr
(37) |
May
(25) |
Jun
(65) |
Jul
(20) |
Aug
(41) |
Sep
(17) |
Oct
(21) |
Nov
(29) |
Dec
(10) |
2018 |
Jan
(1) |
Feb
(8) |
Mar
|
Apr
(9) |
May
(5) |
Jun
(4) |
Jul
(5) |
Aug
(10) |
Sep
(12) |
Oct
(7) |
Nov
|
Dec
(3) |
2019 |
Jan
(16) |
Feb
(3) |
Mar
(33) |
Apr
(2) |
May
(17) |
Jun
(10) |
Jul
|
Aug
(3) |
Sep
(2) |
Oct
|
Nov
(6) |
Dec
(19) |
2020 |
Jan
(6) |
Feb
(8) |
Mar
(6) |
Apr
(17) |
May
(8) |
Jun
(12) |
Jul
(13) |
Aug
(3) |
Sep
(3) |
Oct
(1) |
Nov
(9) |
Dec
|
2021 |
Jan
(1) |
Feb
(8) |
Mar
(7) |
Apr
|
May
(8) |
Jun
(2) |
Jul
(2) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
Make sure you're using reply to. On Sun., Aug. 15, 2021, 2:00 a.m. hung.nguyengia, < hun...@pr...> wrote: > I have my own research meanwhile. It seems due to Google Chrome requiring > MSVC on Windows. But this information is long obsolete. Nowadays Chrome on > Windows was built using Clang. Anyone even try building qtwebengine on > MSYS2 with clang64? It seems it's not a technical problem now but it's the > qt guys not updated their stack as they still insisting on MSVC. > > Sent with ProtonMail Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > On Sunday, August 15th, 2021 at 12:01 PM, Zach Bacon <wow...@gm...> > wrote: > > > Webengine unfortunately is not compilable with mingw compilers > currently, it would need massive patching to make it work and the technical > debt with that wouldn't be that feasible at the current time considering > most of the developers are working in their spare time. > > > > On Sun., Aug. 15, 2021, 12:28 a.m. hung.nguyengia via Msys2-users, < > msy...@li...> wrote: > > > > > Just find out this when building a qtwebengine based browser. The > configuration process failed because of missing qtwebengine and I searched > for the package via pacman -Ss and found nothing. There is only qtwebview > but not even qtwebkit. > > > > > > Please add the qtwebengine and possibly qtwebkit package. Thanks. > > > > > > Sent with ProtonMail Secure Email. > > > > > > _______________________________________________ > > > > > > Msys2-users mailing list > > > > > > Msy...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/msys2-users > |
From: Zach B. <wow...@gm...> - 2021-08-15 05:01:58
|
Webengine unfortunately is not compilable with mingw compilers currently, it would need massive patching to make it work and the technical debt with that wouldn't be that feasible at the current time considering most of the developers are working in their spare time. On Sun., Aug. 15, 2021, 12:28 a.m. hung.nguyengia via Msys2-users, < msy...@li...> wrote: > Just find out this when building a qtwebengine based browser. The > configuration process failed because of missing qtwebengine and I searched > for the package via pacman -Ss and found nothing. There is only qtwebview > but not even qtwebkit. > > Please add the qtwebengine and possibly qtwebkit package. Thanks. > > Sent with ProtonMail Secure Email. > > > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users > |
From: hung.nguyengia <hun...@pr...> - 2021-08-15 04:27:32
|
Just find out this when building a qtwebengine based browser. The configuration process failed because of missing qtwebengine and I searched for the package via pacman -Ss and found nothing. There is only qtwebview but not even qtwebkit. Please add the qtwebengine and possibly qtwebkit package. Thanks. Sent with ProtonMail Secure Email. |
From: Juha L. <juh...@gm...> - 2021-07-24 03:56:48
|
Hi, I started to use MSYS2 recently. to make 64 bit Fortran applications. Everything works fine except when I try to launch the exe directly or via shortcut in the command prompt I get error 0 [main] j3.0_debug (1524) dll_list::form_ntname: WARNING: invalid path name '\??' 2409 [main] j3.0_debug (1524) C:\jUusi\j3.0_debug.exe: *** fatal error - add_item ("\??", "/", ...) failed, errno 22 Stack trace: Frame Function Args 000FFFF8630 00180062835 (00180296FE2, 00180272E41, 0000000003F, 000FFFF8B10) 000FFFF8B60 001800488F2 (00000000000, 00180020010, 000FFFFABB6, 000FFFF9BB0) When I put the exe into a subfolder then it can be launched without problems. What is the problem? Juha Lappi |
From: LIU H. <lh_...@12...> - 2021-07-02 15:38:00
|
在 2021-06-30 21:37, Andrew Lowe 写道: > > Having said all of this, having been in academia for the last 10 years, the whole > git/git-hub/gitlab thing has passed me by so any advice on the best way to make the eventual steps > to create Barry accessible to a wider audience would be greatly appreciated. > For those non-computer scientists or engineers, I believe Python is something simpler, more intuitive and (likely) more useful, than C or C++. Resource management, pointer reachability, undefined behavior, and so on, all require integrated knowledge about computers and ISAs; it's not like 'I want to create a matrix and multiply it with another'. Although our environments (MSYS, MINGW32, MINGW64, UCRT64 and CLANG64), would it be better to provide more specialized pre-configured environments, such as 'Barry for C and C++', 'Barry for Python', etc.? That can also make them smaller so they don't take up too much room on memory sticks. -- Best regards, LIU Hao |
From: Andrew L. <msy...@wh...> - 2021-06-30 13:38:05
|
Dear all, I’ve been a long time lurker on this list and now need your advice/criticism of something that I build using Mysys2. The backstory to this is that I taught, for about 9 years, programming to first year engineering students and for most of them, the whole concept of downloading some sort of IDE, installing it and then navigating through the menu structure to achieve anything was “a bridge too far”. Most of the students would go on to study Civil/Mechanical/Chemical Engineering and were of the mindset “why do I need to learn programming, I’m going to be a XXXXX engineer”. Even though I tried to tell them that ALL fields of engineering do some sort of programming nowadays, they knew better than me and treated the ½ weight subject as something that was a hindrance and would do the least amount of work possible. Hence Barry was created. Barry is an environment that is built using Msys2 and other open source “stuff”. It is meant to be “installed” on a memory stick and in turn plugged into any Windows machine. Fire up the shell and hey presto you have a C/C++ dev environment. All of your work is stored in the /home dir, which is on the stick so your work is always with the environment. Obviously you can just “install” it directly onto the laptop or a desktop as well. The install process is really just unzipping the zipped up environment that I put together into whatever dir you want – no registry was harmed in the creation of Barry :) I’ve been a code monkey for a long time and use Linux, Gentoo, as my default machine but I use it in a pretty “standard” config, I don’t fiddle with .rc files etc. When I set Barry up I did a crash course in bash config but I have a feeling I’m probably doing stuff in a sub-optimal way. If people don’t object I’d like to place the steps, one by one, onto this list and you good people can critique and refine what I’m doing so that I can create something that is both robust and customisable. Having said all of this, having been in academia for the last 10 years, the whole git/git-hub/gitlab thing has passed me by so any advice on the best way to make the eventual steps to create Barry accessible to a wider audience would be greatly appreciated. Regards, Andrew |
From: Andrew L. <msy...@wh...> - 2021-06-18 19:55:27
|
Hi all, I am in need of a Python package that is in 3.9. I also have mingw-w64-x86_64-clang installed. This has brought in mingw-w64-x86_64-python and looking at it's page, https://packages.msys2.org/package/mingw-w64-x86_64-python it is still 3.8.9. How do I find out when it will jump to 3.9.X? Or do I have to install Python3.9 and run the two in, what usually ends up being messy, parallel? Thoughts gratefully appreciated, Andrew |
From: Koichi M. <myo...@gm...> - 2021-05-10 07:55:00
|
2021-05-05 19:22 Koichi Murase <myo...@gm...>: > The problematic keybinding is the following line (.inputrc L79): > > "\C-?": backward-kill-line # Ctrl-BackSpace There has been no reply in this mailing list, but let me report the current status. I found the corresponding repository on GitHub and submitted a PR which has been merged today: https://github.com/msys2/MSYS2-packages/pull/2490 Sorry for the noise. -- Koichi |
From: Koichi M. <myo...@gm...> - 2021-05-05 10:23:03
|
Hello, I'm not sure if this is the right place to report, but there is a problem with .inputrc, so I would like to report it to "msys2 mailing list" mentioned in the comment of .inputrc. Is this the "msys2 mailing list"? If there is another mailing list that is called "msys2 mailing list", I would appreciate it if you could point the mailing list for me. The problematic keybinding is the following line (.inputrc L79): "\C-?": backward-kill-line # Ctrl-BackSpace (1) It's usually ineffective---this keybinding is usually overwritten by the readline just before Bash shows the prompt, so is normally ineffective. One can confirm this by putting the following line at the end of .bashrc: # At the end of ~/.bashrc bind -p | grep '"\\C-?"' and start the Bash session, and input and run the same command (bind -p | grep '"\\C-?"') again. The result will be "\C-?": backward-kill-line $ bind -p | grep '"\\C-?"' "\C-?": backward-delete-char The first line shows the settings at the time point running .bashrc, and the third line shows the setting after Bash started to prompt user commands. You can see that the keybinding "backward-kill-line" set up by .inputrc is overwritten by "backward-delete-char" while the initialization process of Bash itself. (2) It causes unintended behavior---The comment says Control-BackSpace, but it actually binds to BackSpace. When it becomes effective, it results in unintuitive behavior, which confuses users. For example, one can make it effective by reloading .inputrc by pressing "\C-x\C-r" [i.e., press Control+x and then Control+r]. Then, Backspace (without Control modifier) starts to delete everything before the current cursor position. It is clear from the comment ("# Ctrl-BackSpace") that the intent of this keybinding is to change the behavior of Ctrl-BackSpace, so the actual effect that changes the behavior of Backspace is unintended. # To explain the background in more detail, actually, the escape # sequences of Backspace and Ctrl-Backspace depend on the terminal. # But, in modern terminal emulators, "\C-?" is definitely the escape # sequence of "Backspace" / "DEL" (without Ctrl modifier) but not the # escape sequence of "Ctrl-BackSpace". Only some of the very old # terminals send "\C-h" for Backspace and "\C-?" for Ctrl-Backspace. # Modern terminal emulators typically send "\C-?" for Backspace and # "\C-_" for Ctrl-Backspace. Some send "\C-?" for Backspace and "\C-h" # for Ctrl-Backspace. Some minor terminals such as Windows Terminal # seem to send "\C-?" for Backspace and "\C-w" for Ctrl-Backspace. For # this historical variations, Bash/Readline actually tries to # overwrite the settings based on the current TERM environment # variable using the termcap/terminfo database, which is the reason # why the keybinding is ineffective by default. # # This keybinding caused a real problem with a Bash setting ble.sh # reported at https://github.com/akinomyoga/ble.sh/issues/104 . ble.sh # is a replacement for Readline and don't overwrite the keybindings # set by users. So, the keybinding became effective and caused the # unintuitive behavior. I'd recommend just removing this keybinding since it has been ineffective and even no one seems to have noticed that until now. Maybe it works in some old terminal used by the one who added this keybinding, but such an environment-dependent setting broken in the typical terminals should not enter the default .inputrc. If the maintainers think this keybinding is really needed for the default MSYS2 setting, I recommend switching the escape sequence from "\C-?" to "\C-_". Maybe one can optionally add another keybinding "\C-h": backward-kill-line, but this again causes a similar problem in some terminals because "\C-h" is sometimes Backspace, so I don't think such a keybinding should be set up by the default .inputrc. Thank you, Koichi |
From: Jeroen O. <je...@be...> - 2021-05-01 22:30:59
|
I think you need to add a SigLevel to your pacman.conf, for example: [custom] Server = file:///home/vincent.torri/custompkg SigLevel = Never On Sat, May 1, 2021 at 11:25 PM Vincent Torri <vin...@gm...> wrote: > > Hello, > > I have an error when trying to create a custom repository for my > packages. Here are the steps : > > 1) I have created a package with makepkg-mingw : > mingw-w64-x86_64-efl-regex-1.2.2-1-any.pkg.tar.zst > > 2) i have created the directory $HOME/custompkg > > 3) i have copied mingw-w64-x86_64-efl-regex-1.2.2-1-any.pkg.tar.zst in > $HOME/custompkg > > 4) in /etc/pacman.conf, I have added at the end : > > [custom] > Server = file:///home/vincent.torri/custompkg > > 5) I have added the package to the local repo : > > repo-add custompkg/custom.db.tar.zst > custompkg/mingw-w64-x86_64-efl-regex-1.2.2-1-any.pkg.tar.zst > > 6) then I try to install my package : > > pacman -S efl-regex > > The I have this error : > error: custom: missing required signature > error: database 'custom' is not valid (invalid or corrupted database > (PGP signature)) > > Does someone know what I have missed ? Are all my steps above correct ? > > thank you > > Vincent Torri > > > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users |
From: Zach B. <wow...@gm...> - 2021-05-01 22:05:24
|
Sorry I meant mingw-w64-x86_64-efl-regex The x86_64 being the the mingw toolchain you used to compile the package. On Sat., May 1, 2021, 5:40 p.m. Vincent Torri, <vin...@gm...> wrote: > On Sat, May 1, 2021 at 11:34 PM Zach Bacon <wow...@gm...> wrote: > > > > so what you have a is a mingw-w64 package, so you need to run in this > case pacman -S mingw-w64-efl-regex > > $ pacman -S mingw-w64-efl-regex > error: target not found: mingw-w64-efl-regex > > Vincent Torri > > > > On Sat, May 1, 2021 at 5:26 PM Vincent Torri <vin...@gm...> > wrote: > >> > >> Hello, > >> > >> I have an error when trying to create a custom repository for my > >> packages. Here are the steps : > >> > >> 1) I have created a package with makepkg-mingw : > >> mingw-w64-x86_64-efl-regex-1.2.2-1-any.pkg.tar.zst > >> > >> 2) i have created the directory $HOME/custompkg > >> > >> 3) i have copied mingw-w64-x86_64-efl-regex-1.2.2-1-any.pkg.tar.zst in > >> $HOME/custompkg > >> > >> 4) in /etc/pacman.conf, I have added at the end : > >> > >> [custom] > >> Server = file:///home/vincent.torri/custompkg > >> > >> 5) I have added the package to the local repo : > >> > >> repo-add custompkg/custom.db.tar.zst > >> custompkg/mingw-w64-x86_64-efl-regex-1.2.2-1-any.pkg.tar.zst > >> > >> 6) then I try to install my package : > >> > >> pacman -S efl-regex > >> > >> The I have this error : > >> error: custom: missing required signature > >> error: database 'custom' is not valid (invalid or corrupted database > >> (PGP signature)) > >> > >> Does someone know what I have missed ? Are all my steps above correct ? > >> > >> thank you > >> > >> Vincent Torri > >> > >> > >> _______________________________________________ > >> Msys2-users mailing list > >> Msy...@li... > >> https://lists.sourceforge.net/lists/listinfo/msys2-users > |
From: Vincent T. <vin...@gm...> - 2021-05-01 21:40:37
|
On Sat, May 1, 2021 at 11:34 PM Zach Bacon <wow...@gm...> wrote: > > so what you have a is a mingw-w64 package, so you need to run in this case pacman -S mingw-w64-efl-regex $ pacman -S mingw-w64-efl-regex error: target not found: mingw-w64-efl-regex Vincent Torri > On Sat, May 1, 2021 at 5:26 PM Vincent Torri <vin...@gm...> wrote: >> >> Hello, >> >> I have an error when trying to create a custom repository for my >> packages. Here are the steps : >> >> 1) I have created a package with makepkg-mingw : >> mingw-w64-x86_64-efl-regex-1.2.2-1-any.pkg.tar.zst >> >> 2) i have created the directory $HOME/custompkg >> >> 3) i have copied mingw-w64-x86_64-efl-regex-1.2.2-1-any.pkg.tar.zst in >> $HOME/custompkg >> >> 4) in /etc/pacman.conf, I have added at the end : >> >> [custom] >> Server = file:///home/vincent.torri/custompkg >> >> 5) I have added the package to the local repo : >> >> repo-add custompkg/custom.db.tar.zst >> custompkg/mingw-w64-x86_64-efl-regex-1.2.2-1-any.pkg.tar.zst >> >> 6) then I try to install my package : >> >> pacman -S efl-regex >> >> The I have this error : >> error: custom: missing required signature >> error: database 'custom' is not valid (invalid or corrupted database >> (PGP signature)) >> >> Does someone know what I have missed ? Are all my steps above correct ? >> >> thank you >> >> Vincent Torri >> >> >> _______________________________________________ >> Msys2-users mailing list >> Msy...@li... >> https://lists.sourceforge.net/lists/listinfo/msys2-users |
From: Vincent T. <vin...@gm...> - 2021-05-01 21:25:52
|
Hello, I have an error when trying to create a custom repository for my packages. Here are the steps : 1) I have created a package with makepkg-mingw : mingw-w64-x86_64-efl-regex-1.2.2-1-any.pkg.tar.zst 2) i have created the directory $HOME/custompkg 3) i have copied mingw-w64-x86_64-efl-regex-1.2.2-1-any.pkg.tar.zst in $HOME/custompkg 4) in /etc/pacman.conf, I have added at the end : [custom] Server = file:///home/vincent.torri/custompkg 5) I have added the package to the local repo : repo-add custompkg/custom.db.tar.zst custompkg/mingw-w64-x86_64-efl-regex-1.2.2-1-any.pkg.tar.zst 6) then I try to install my package : pacman -S efl-regex The I have this error : error: custom: missing required signature error: database 'custom' is not valid (invalid or corrupted database (PGP signature)) Does someone know what I have missed ? Are all my steps above correct ? thank you Vincent Torri |
From: Norbert P. <nor...@gm...> - 2021-05-01 11:44:44
|
use the -s flag for makepkg to automatically install required dependencies Am Sa., 1. Mai 2021 um 09:17 Uhr schrieb Vincent Torri < vin...@gm...>: > Hello > > I ma trying to package a project for mingw (not msys) and I have some > missing dependencies when i run makepkg-mingw : > > > $ makepkg-mingw > ==> Making package: mingw-w64-efl 1.25.99.66566.g994f520bfd-1 (Sat May > 1 09:14:45 2021) > ==> Checking runtime dependencies... > ==> Missing dependencies: > -> mingw-w64-x86_64-libsndfile > -> mingw-w64-x86_64-libavif > -> mingw-w64-x86_64-luajit > -> mingw-w64-x86_64-bullet > -> mingw-w64-x86_64-gstreamer > -> mingw-w64-x86_64-gst-plugins-base > -> mingw-w64-x86_64-gst-plugins-good > -> mingw-w64-x86_64-gst-libav > ==> Checking buildtime dependencies... > ==> Missing dependencies: > -> mingw-w64-x86_64-meson > ==> ERROR: Could not resolve all dependencies. > > I have attached the PKGBUILD > > Does someone know what is wrong ? > > thank you > > Vincent Torri > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users > |
From: Vincent T. <vin...@gm...> - 2021-05-01 07:17:21
|
Hello I ma trying to package a project for mingw (not msys) and I have some missing dependencies when i run makepkg-mingw : $ makepkg-mingw ==> Making package: mingw-w64-efl 1.25.99.66566.g994f520bfd-1 (Sat May 1 09:14:45 2021) ==> Checking runtime dependencies... ==> Missing dependencies: -> mingw-w64-x86_64-libsndfile -> mingw-w64-x86_64-libavif -> mingw-w64-x86_64-luajit -> mingw-w64-x86_64-bullet -> mingw-w64-x86_64-gstreamer -> mingw-w64-x86_64-gst-plugins-base -> mingw-w64-x86_64-gst-plugins-good -> mingw-w64-x86_64-gst-libav ==> Checking buildtime dependencies... ==> Missing dependencies: -> mingw-w64-x86_64-meson ==> ERROR: Could not resolve all dependencies. I have attached the PKGBUILD Does someone know what is wrong ? thank you Vincent Torri |
From: Hannes D. <ss...@ya...> - 2021-03-02 16:24:41
|
Am Dienstag, 2. März 2021, 13:36:31 MEZ hat Burkhardt, Glenn B Collins via Msys2-users <msy...@li...> Folgendes geschrieben: > Neither gdb 9.2-3 nor mingw-w64-x86_64-gdb 10.1-2 are able to set breakpoints in code compiled with mingw-w64-x86_64-gcc 10.2.0-6. Anyone else seen this? Thanks. > > $ g++ --version > g++.exe (Rev6, Built by MSYS2 project) 10.2.0 > > $ cat t.cpp > #define __USE_MINGW_ANSI_STDIO 1 > #include <stdio.h> > > int main() > { > size_t z = 0; > > printf("%zu\n", z); > } > > Glenn.Burkhardt@AI234087 MSYS ~ > $ g++ -g t.cpp -o t > > $ gdb ./t > GNU gdb (GDB) 9.2 > Copyright (C) 2020 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Type "show copying" and "show warranty" for details. > This GDB was configured as "x86_64-pc-msys". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>. > Find the GDB manual and other documentation resources online at: > <http://www.gnu.org/software/gdb/documentation/>. > > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Traceback (most recent call last): > File "<string>", line 3, in <module> > ModuleNotFoundError: No module named 'libstdcxx' > /etc/gdbinit:6: Error in sourced command file: > Error while executing Python code. > Reading symbols from ./t... > (gdb) b main > Breakpoint 1 at 0x14000154d: file t.cpp, line 6. > (gdb) l > 1 #define __USE_MINGW_ANSI_STDIO 1 > 2 #include <stdio.h> > 3 > 4 int main() > 5 { > 6 size_t z = 0; > 7 > 8 printf("%zu\n", z); > 9 } > (gdb) b 8 > Breakpoint 2 at 0x140001555: file t.cpp, line 8. > (gdb) r > Starting program: /home/glenn.burkhardt/t > [New Thread 42340.0xaee8] > Warning: > Cannot insert breakpoint 1. > Cannot access memory at address 0x140001548 > Cannot insert breakpoint 2. > Cannot access memory at address 0x140001555 > > Command aborted. This looks like gdb doesn't understand ASLR, like this bug: https://sourceware.org/bugzilla/show_bug.cgi?id=26037 But it was fixed for gdb-10.1. Hannes |
From: Burkhardt, G. B C. <Gle...@co...> - 2021-03-02 16:19:53
|
The current Msys2 debugger is at 9.2.3: gdb 9.2-3 GNU Debugger (MSYS2 version) As mentioned in another email, the mingw-w64-x86_64-gdb 10.1-2 does handle breakpoints correctly, so I'll try a 10.x Msys2 version of gdb when it becomes available. -----Original Message----- From: Hannes Domani <ss...@ya...> Sent: Tuesday, March 2, 2021 11:04 To: msy...@li...; Burkhardt, Glenn B Collins <Gle...@co...> Subject: [External] Re: [Msys2-users] gdb can't set breakpoint Am Dienstag, 2. März 2021, 13:36:31 MEZ hat Burkhardt, Glenn B Collins via Msys2-users <msy...@li...> Folgendes geschrieben: > Neither gdb 9.2-3 nor mingw-w64-x86_64-gdb 10.1-2 are able to set breakpoints in code compiled with mingw-w64-x86_64-gcc 10.2.0-6. Anyone else seen this? Thanks. > > $ g++ --version > g++.exe (Rev6, Built by MSYS2 project) 10.2.0 > > $ cat t.cpp > #define __USE_MINGW_ANSI_STDIO 1 > #include <stdio.h> > > int main() > { > size_t z = 0; > > printf("%zu\n", z); > } > > Glenn.Burkhardt@AI234087 MSYS ~ > $ g++ -g t.cpp -o t > > $ gdb ./t > GNU gdb (GDB) 9.2 > Copyright (C) 2020 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later ><https://urldefense.com/v3/__http://gnu.org/licenses/gpl.html__;!!MvWE!TEX72QtS2qc-oTW9x0AP_BzAB4NS_bGSBpHUJqorVVzNeNABvPLDqDFjlEOM7vC5ze9JwA$ > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Type "show copying" and "show warranty" for details. > This GDB was configured as "x86_64-pc-msys". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <https://urldefense.com/v3/__http://www.gnu.org/software/gdb/bugs/__;!!MvWE!TEX72QtS2qc-oTW9x0AP_BzAB4NS_bGSBpHUJqorVVzNeNABvPLDqDFjlEOM7vD0880wPQ$ >. > Find the GDB manual and other documentation resources online at: > <https://urldefense.com/v3/__http://www.gnu.org/software/gdb/documentation/__;!!MvWE!TEX72QtS2qc-oTW9x0AP_BzAB4NS_bGSBpHUJqorVVzNeNABvPLDqDFjlEOM7vBdnGW48w$ >. > > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Traceback (most recent call last): > File "<string>", line 3, in <module> > ModuleNotFoundError: No module named 'libstdcxx' > /etc/gdbinit:6: Error in sourced command file: > Error while executing Python code. > Reading symbols from ./t... > (gdb) b main > Breakpoint 1 at 0x14000154d: file t.cpp, line 6. > (gdb) l > 1 #define __USE_MINGW_ANSI_STDIO 1 > 2 #include <stdio.h> > 3 > 4 int main() > 5 { > 6 size_t z = 0; > 7 > 8 printf("%zu\n", z); > 9 } > (gdb) b 8 > Breakpoint 2 at 0x140001555: file t.cpp, line 8. > (gdb) r > Starting program: /home/glenn.burkhardt/t [New Thread 42340.0xaee8] > Warning: > Cannot insert breakpoint 1. > Cannot access memory at address 0x140001548 Cannot insert breakpoint >2. > Cannot access memory at address 0x140001555 > > Command aborted. This looks like gdb doesn't understand ASLR, like this bug: https://urldefense.com/v3/__https://sourceware.org/bugzilla/show_bug.cgi?id=26037__;!!MvWE!TEX72QtS2qc-oTW9x0AP_BzAB4NS_bGSBpHUJqorVVzNeNABvPLDqDFjlEOM7vA6x8489Q$ But it was fixed for gdb-10.1. Hannes |
From: Hannes D. <ss...@ya...> - 2021-03-02 16:16:21
|
Am Dienstag, 2. März 2021, 15:37:39 MEZ hat Burkhardt, Glenn B Collins via Msys2-users <msy...@li...> Folgendes geschrieben: > Command line editing isn't available for me in mingw-w64-x86_64-gdb 10.1-2 in the Msys2 shell. I notice that it has been linked with /mingw64/bin/libreadline8.dll. Is there any way to get it to work? If you're on Win10, you could try to enable the pseudo console. Set in mingw64.ini: MSYS=enable_pcon Hannes |
From: Burkhardt, G. B C. <Gle...@co...> - 2021-03-02 16:14:11
|
I assume that you mean then to start another Msys2 shell. That didn't work, nor did appending ":enable_pcon" to set MSYS=winsymlinks:nativestrict in msys2_shell.cmd, which is how I start my Msys2 shell. Thanks. -----Original Message----- From: Hannes Domani <ss...@ya...> Sent: Tuesday, March 2, 2021 11:06 To: msy...@li...; Burkhardt, Glenn B Collins <Gle...@co...> Subject: [External] Re: [Msys2-users] command line editing in mingw-w64-x86_64-gdb 10.1-2 Am Dienstag, 2. März 2021, 15:37:39 MEZ hat Burkhardt, Glenn B Collins via Msys2-users <msy...@li...> Folgendes geschrieben: > Command line editing isn't available for me in mingw-w64-x86_64-gdb 10.1-2 in the Msys2 shell. I notice that it has been linked with /mingw64/bin/libreadline8.dll. Is there any way to get it to work? If you're on Win10, you could try to enable the pseudo console. Set in mingw64.ini: MSYS=enable_pcon Hannes |
From: Burkhardt, G. B C. <Gle...@co...> - 2021-03-02 14:37:25
|
Command line editing isn't available for me in mingw-w64-x86_64-gdb 10.1-2 in the Msys2 shell. I notice that it has been linked with /mingw64/bin/libreadline8.dll. Is there any way to get it to work? Unfortunately, Msys2 version of gdb in the gdb 9.2-3, which does support command line editing, doesn't work with executables created by the mingw-w64-x86_64-gcc 10.2.0-6 'gcc'. Breakpoints can't be set. |
From: Burkhardt, G. B C. <Gle...@co...> - 2021-03-02 14:20:03
|
Command line editing isn't available for me in mingw-w64-x86_64-gdb 10.1-2 in the Msys2 shell. I notice that it has been linked with . Is there any way to get it to work? Unfortunately, Msys2 version of gdb in the gdb 9.2-3, which does support command line editing, doesn't work with executables created by the mingw-w64-x86_64-gcc 10.2.0-6 'gcc'. Breakpoints can't be set. |
From: Burkhardt, G. B C. <Gle...@co...> - 2021-03-02 12:36:12
|
Neither gdb 9.2-3 nor mingw-w64-x86_64-gdb 10.1-2 are able to set breakpoints in code compiled with mingw-w64-x86_64-gcc 10.2.0-6. Anyone else seen this? Thanks. $ g++ --version g++.exe (Rev6, Built by MSYS2 project) 10.2.0 $ cat t.cpp #define __USE_MINGW_ANSI_STDIO 1 #include <stdio.h> int main() { size_t z = 0; printf("%zu\n", z); } Glenn.Burkhardt@AI234087 MSYS ~ $ g++ -g t.cpp -o t $ gdb ./t GNU gdb (GDB) 9.2 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-msys". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Traceback (most recent call last): File "<string>", line 3, in <module> ModuleNotFoundError: No module named 'libstdcxx' /etc/gdbinit:6: Error in sourced command file: Error while executing Python code. Reading symbols from ./t... (gdb) b main Breakpoint 1 at 0x14000154d: file t.cpp, line 6. (gdb) l 1 #define __USE_MINGW_ANSI_STDIO 1 2 #include <stdio.h> 3 4 int main() 5 { 6 size_t z = 0; 7 8 printf("%zu\n", z); 9 } (gdb) b 8 Breakpoint 2 at 0x140001555: file t.cpp, line 8. (gdb) r Starting program: /home/glenn.burkhardt/t [New Thread 42340.0xaee8] Warning: Cannot insert breakpoint 1. Cannot access memory at address 0x140001548 Cannot insert breakpoint 2. Cannot access memory at address 0x140001555 Command aborted. |
From: Stephen L. <ste...@st...> - 2021-02-15 01:04:49
|
Norbert Pfeiler <nor...@gm...> writes: > probably this > https://www.msys2.org/news/#2020-06-29-new-packagers Ah, that makes sense. Apparently I missed the announcement about this last June. Thanks. -- -- Stephe |
From: Norbert P. <nor...@gm...> - 2021-02-15 00:13:30
|
probably this https://www.msys2.org/news/#2020-06-29-new-packagers Am Mo., 15. Feb. 2021 um 00:21 Uhr schrieb Stephen Leake < ste...@st...>: > Luke Robison <luk...@gm...> writes: > > > The msys2 homepage has instructions for you. > > > > https://www.msys2.org/ > > Hmm. That does not mention "trust" > > Perhaps you are saying I need to reinstall from scratch? Why would that > fix this issue - it appears there is an untrusted signature in the msys > repository. > > > > On Sun, Feb 14, 2021, 12:21 PM Stephen Leake < > ste...@st...> > > wrote: > > > >> I'm trying to update several packages to the current version, so I start > >> with 'pacman -Sy'. That gives: > >> > >> error: mingw32: signature from "David Macek <dav...@gm...>" > is > >> marginal trust > >> error: failed to update mingw32 (invalid or corrupted database (PGP > >> signature)) > >> > >> and similar for mingw64 and msys. > >> > >> Is there a way to ignore or fix this? (pacman -Sy --force did not help) > >> > >> -- > >> -- Stephe > >> > >> > >> _______________________________________________ > >> Msys2-users mailing list > >> Msy...@li... > >> https://lists.sourceforge.net/lists/listinfo/msys2-users > >> > > > > > > -- > -- Stephe > > > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users > |
From: Stephen L. <ste...@st...> - 2021-02-14 23:21:35
|
Luke Robison <luk...@gm...> writes: > The msys2 homepage has instructions for you. > > https://www.msys2.org/ Hmm. That does not mention "trust" Perhaps you are saying I need to reinstall from scratch? Why would that fix this issue - it appears there is an untrusted signature in the msys repository. > On Sun, Feb 14, 2021, 12:21 PM Stephen Leake <ste...@st...> > wrote: > >> I'm trying to update several packages to the current version, so I start >> with 'pacman -Sy'. That gives: >> >> error: mingw32: signature from "David Macek <dav...@gm...>" is >> marginal trust >> error: failed to update mingw32 (invalid or corrupted database (PGP >> signature)) >> >> and similar for mingw64 and msys. >> >> Is there a way to ignore or fix this? (pacman -Sy --force did not help) >> >> -- >> -- Stephe >> >> >> _______________________________________________ >> Msys2-users mailing list >> Msy...@li... >> https://lists.sourceforge.net/lists/listinfo/msys2-users >> > > -- -- Stephe |