[Touch-packages] [Bug 2059856] Re: gdb 10.0 fails to examine any global variables in D programs
** Merge proposal linked:
https://code.launchpad.net/~liushuyu-011/ubuntu/+source/gdb/+git/gdb/+merge/463546
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2059856
Title:
gdb 10.0 fails to examine any global variables in D programs
Status in gdb:
Fix Released
Status in gdb package in Ubuntu:
New
Bug description:
[ Impact ]
* GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
* LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test images.
[ Test Plan ]
Considering the following D program:
```
module t;
class uv {
int i;
}
__gshared uv i;
int main() {
i = new uv();
return 0; // #break
}
```
If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`,
run the GDB using the following commands ...
```
b t.d:10
p t.i
```
... you will notice GDB will complain that "'t.i' has unknown type;
cast it to its declared type."
[ Where problems could occur ]
* The fix consists of a single line change to the demangler. The worst-case
scenario would be breaking the demangling functionality of other programming
languages. However, the newer D ABI uses a symbol mangling scheme that is very
difficult to confuse with other programming languages.
* Incorrect symbol de-mangling may also cause user confusion. However, the
patch fixed a fundamental usability issue.
[ Other Info ]
* Initial discussion in the LDC2 bug tracker:
https://github.com/ldc-developers/ldc/issues/4389
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2059856/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059856] Re: gdb 10.0 fails to examine any global variables in D programs
** Description changed:
[ Impact ]
* GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
* LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test images.
[ Test Plan ]
Considering the following D program:
```
module t;
class uv {
int i;
}
__gshared uv i;
int main() {
i = new uv();
return 0; // #break
}
```
If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`, run
the GDB using the following commands ...
```
b t.d:10
p t.i
```
... you will notice GDB will complain that "'t.i' has unknown type; cast
it to its declared type."
[ Where problems could occur ]
- * The fix consists of a single line change to the demangler. The worst-case
scenario would be breaking the demangling functionality of other programming
languages. However, the newer D ABI uses a symbol mangling scheme that is very
difficult to confuse with other programming languages.
- * Incorrect symbol de-mangling may also cause user confusion. However, the
patch fixed a fundamental usability issue.
+ * The fix consists of a single line change to the demangler. The worst-case
scenario would be breaking the demangling functionality of other programming
languages. However, the newer D ABI uses a symbol mangling scheme that is very
difficult to confuse with other programming languages.
+ * Incorrect symbol de-mangling may also cause user confusion. However, the
patch fixed a fundamental usability issue.
+
+ [ Other Info ]
+
+ * Initial discussion in the LDC2 bug tracker: https://github.com/ldc-
+ developers/ldc/issues/4389
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2059856
Title:
gdb 10.0 fails to examine any global variables in D programs
Status in gdb:
Confirmed
Status in gdb package in Ubuntu:
New
Bug description:
[ Impact ]
* GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
* LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test images.
[ Test Plan ]
Considering the following D program:
```
module t;
class uv {
int i;
}
__gshared uv i;
int main() {
i = new uv();
return 0; // #break
}
```
If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`,
run the GDB using the following commands ...
```
b t.d:10
p t.i
```
... you will notice GDB will complain that "'t.i' has unknown type;
cast it to its declared type."
[ Where problems could occur ]
* The fix consists of a single line change to the demangler. The worst-case
scenario would be breaking the demangling functionality of other programming
languages. However, the newer D ABI uses a symbol mangling scheme that is very
difficult to confuse with other programming languages.
* Incorrect symbol de-mangling may also cause user confusion. However, the
patch fixed a fundamental usability issue.
[ Other Info ]
* Initial discussion in the LDC2 bug tracker:
https://github.com/ldc-developers/ldc/issues/4389
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2059856/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059856] Re: gdb 10.0 fails to examine any global variables in D programs
** Description changed:
- Summary:
+ [ Impact ]
- * GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
- * LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test images.
+ * GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
+ * LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test images.
- Reproduce steps:
+ [ Test Plan ]
Considering the following D program:
```
module t;
class uv {
- int i;
+ int i;
}
__gshared uv i;
int main() {
- i = new uv();
- return 0; // #break
+ i = new uv();
+ return 0; // #break
}
```
If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`, run
the GDB using the following commands ...
```
b t.d:10
p t.i
```
... you will notice GDB will complain that "'t.i' has unknown type; cast
it to its declared type."
+
+ [ Where problems could occur ]
+
+ * The fix consists of a single line change to the demangler. The worst-case
scenario would be breaking the demangling functionality of other programming
languages. However, the newer D ABI uses a symbol mangling scheme that is very
difficult to confuse with other programming languages.
+ * Incorrect symbol de-mangling may also cause user confusion. However, the
patch fixed a fundamental usability issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2059856
Title:
gdb 10.0 fails to examine any global variables in D programs
Status in gdb:
Confirmed
Status in gdb package in Ubuntu:
New
Bug description:
[ Impact ]
* GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
* LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test images.
[ Test Plan ]
Considering the following D program:
```
module t;
class uv {
int i;
}
__gshared uv i;
int main() {
i = new uv();
return 0; // #break
}
```
If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`,
run the GDB using the following commands ...
```
b t.d:10
p t.i
```
... you will notice GDB will complain that "'t.i' has unknown type;
cast it to its declared type."
[ Where problems could occur ]
* The fix consists of a single line change to the demangler. The worst-case
scenario would be breaking the demangling functionality of other programming
languages. However, the newer D ABI uses a symbol mangling scheme that is very
difficult to confuse with other programming languages.
* Incorrect symbol de-mangling may also cause user confusion. However, the
patch fixed a fundamental usability issue.
[ Other Info ]
* Initial discussion in the LDC2 bug tracker:
https://github.com/ldc-developers/ldc/issues/4389
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2059856/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059856] [NEW] gdb 10.0 fails to examine any global variables in D programs
Public bug reported:
Summary:
* GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
* LDC2 and GDC upstream stated Focal does not have such a problem and stuck to
this release for their test images.
Reproduce steps:
Considering the following D program:
```
module t;
class uv {
int i;
}
__gshared uv i;
int main() {
i = new uv();
return 0; // #break
}
```
If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`, run
the GDB using the following commands ...
```
b t.d:10
p t.i
```
... you will notice GDB will complain that "'t.i' has unknown type; cast
it to its declared type."
** Affects: gdb
Importance: Medium
Status: Confirmed
** Affects: gdb (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Sourceware.org Bugzilla #31580
https://sourceware.org/bugzilla/show_bug.cgi?id=31580
** Also affects: gdb via
https://sourceware.org/bugzilla/show_bug.cgi?id=31580
Importance: Unknown
Status: Unknown
** Changed in: gdb (Ubuntu)
Milestone: None => jammy-updates
** Summary changed:
- gdb 12.1 fails to examine any global variables in D programs
+ gdb 10.0 fails to examine any global variables in D programs
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2059856
Title:
gdb 10.0 fails to examine any global variables in D programs
Status in gdb:
Confirmed
Status in gdb package in Ubuntu:
New
Bug description:
Summary:
* GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
* LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test images.
Reproduce steps:
Considering the following D program:
```
module t;
class uv {
int i;
}
__gshared uv i;
int main() {
i = new uv();
return 0; // #break
}
```
If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`,
run the GDB using the following commands ...
```
b t.d:10
p t.i
```
... you will notice GDB will complain that "'t.i' has unknown type;
cast it to its declared type."
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2059856/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059172] [NEW] autopkgtest failure with perl/5.38.2-3.2
Public bug reported:
autopkgtest failed with
(https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/arm64/p/perl/20240326_162839_855b1@/log.gz):
3968s control.t: warning: can't parse dependency ${t64:Provides}
3968s
3968s # Failed test 'Breaks for libfilter-perl in libperl5.38t64 implies
Provides'
3968s # at debian/t/control.t line 267.
3968s
3968s # Failed test 'Breaks for libfilter-perl in libperl5.38t64 implies
Replaces'
3968s # at debian/t/control.t line 269.
3968s Use of uninitialized value $replaced_version in substitution (s///) at
debian/t/control.t line 273.
3969s
3969s # Failed test 'Replaces version for libfilter-perl in libperl5.38t64
matches Breaks'
3969s # at debian/t/control.t line 274.
3969s # got: undef
3969s # expected: '1.64'
3969s
3969s # Failed test 'Provides version for libfilter-perl in libperl5.38t64
matches Breaks'
3969s # at debian/t/control.t line 280.
3969s # got: ''
3969s # expected: '1.64'
3969s # s/libfilter-perl,/libfilter-perl (= 1.64),/
3969s # Looks like you failed 4 tests of 626.
3969s debian/t/control.t ..
3969s Dubious, test returned 4 (wstat 1024, 0x400)
3969s Failed 4/626 subtests
3969s (less 214 skipped subtests: 408 okay)
** Affects: perl (Ubuntu)
Importance: Undecided
Status: New
** Tags: time-t
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/2059172
Title:
autopkgtest failure with perl/5.38.2-3.2
Status in perl package in Ubuntu:
New
Bug description:
autopkgtest failed with
(https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/arm64/p/perl/20240326_162839_855b1@/log.gz):
3968s control.t: warning: can't parse dependency ${t64:Provides}
3968s
3968s # Failed test 'Breaks for libfilter-perl in libperl5.38t64 implies
Provides'
3968s # at debian/t/control.t line 267.
3968s
3968s # Failed test 'Breaks for libfilter-perl in libperl5.38t64 implies
Replaces'
3968s # at debian/t/control.t line 269.
3968s Use of uninitialized value $replaced_version in substitution (s///) at
debian/t/control.t line 273.
3969s
3969s # Failed test 'Replaces version for libfilter-perl in libperl5.38t64
matches Breaks'
3969s # at debian/t/control.t line 274.
3969s # got: undef
3969s # expected: '1.64'
3969s
3969s # Failed test 'Provides version for libfilter-perl in libperl5.38t64
matches Breaks'
3969s # at debian/t/control.t line 280.
3969s # got: ''
3969s # expected: '1.64'
3969s # s/libfilter-perl,/libfilter-perl (= 1.64),/
3969s # Looks like you failed 4 tests of 626.
3969s debian/t/control.t ..
3969s Dubious, test returned 4 (wstat 1024, 0x400)
3969s Failed 4/626 subtests
3969s (less 214 skipped subtests: 408 okay)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/2059172/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2057704] Re: jackd2 FTBFS due to waflib incompatible with Python 3.12
** Merge proposal linked: https://code.launchpad.net/~liushuyu-011/ubuntu/+source/jackd2/+git/jackd2/+merge/462267 ** Changed in: jackd2 (Ubuntu) Assignee: (unassigned) => Zixing Liu (liushuyu-011) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/2057704 Title: jackd2 FTBFS due to waflib incompatible with Python 3.12 Status in jackd2 package in Ubuntu: New Bug description: jackd2 is now unbuildable after Python 3.12 due to a very outdated WAF build system inside. The upstream has already fixed the issue in a recent commit, we need to introduce this as a patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2057704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2057704] [NEW] jackd2 FTBFS due to waflib incompatible with Python 3.12
Public bug reported: jackd2 is now unbuildable after Python 3.12 due to a very outdated WAF build system inside. The upstream has already fixed the issue in a recent commit, we need to introduce this as a patch. ** Affects: jackd2 (Ubuntu) Importance: Undecided Assignee: Zixing Liu (liushuyu-011) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/2057704 Title: jackd2 FTBFS due to waflib incompatible with Python 3.12 Status in jackd2 package in Ubuntu: New Bug description: jackd2 is now unbuildable after Python 3.12 due to a very outdated WAF build system inside. The upstream has already fixed the issue in a recent commit, we need to introduce this as a patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2057704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2041396] Re: gdb 12.1 generates SIGILL on armhf
> The where problems could occur section says "it is possible that this
fix may break ARM64 execution". How was it verified that this is not
broken?
I believe this could be verified by running the GDB tests inside the Rust
testing suite.
Should I queue an autopkgtest against rustc for GDB in this case?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2041396
Title:
gdb 12.1 generates SIGILL on armhf
Status in gdb:
Fix Released
Status in gdb package in Ubuntu:
Fix Released
Status in gdb source package in Jammy:
Incomplete
Bug description:
[ Impact ]
* GDB 12.1 introduced a regression where it will break program execution
when the program contains mixed ARM code and THUMB code.
* Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.
[ Test Plan ]
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
GDB using the following commands ...
```
b 3
r
c
```
(you can save the contents above to a file and run GDB using `gdb -x
script ./repro`)
... you will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
[ Where problems could occur ]
* GDB is a complex software. As the patch suggests, it may break other use
cases (like single-stepping) entirely.
* Since this is an ARM-only patch, it's unlikely to affect other CPU
architectures. However, it is possible that this fix may break ARM64 execution.
[ Other Info ]
* This bug has been fixed in GDB 13, but the fix was never backported to GDB
12. You can find the upstream bug in the remote bug watch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2041396] Re: gdb 12.1 generates SIGILL on armhf
Verification Report
===
The test is conducted on an RK3399 device (with 4x ARM Cortex-A53 cores
+ 2x ARM Cortex-A72 cores).
Test (1) original Rust program test (associated-types.rs)
-
GDB 12.1-0ubuntu1~22.04 (unpatched)
Rust 1.70.0+dfsg0ubuntu1~bpo2-0ubuntu0.22.04.2
Test program source: https://github.com/rust-
lang/rust/blob/1.68.2/tests/debuginfo/associated-types.rs
GDB script content:
```
b associated-types.rs:111
r
c
```
Result:
```
Breakpoint 1 at 0x4838: file associated-types.rs, line 111.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Breakpoint 1, associated_types::assoc_struct (arg=...) at
associated-types.rs:111
111 zzz(); // #break
Program received signal SIGILL, Illegal instruction.
0x00404ec4 in core::slice::cmp::{impl#5}::equal (self=..., other=...)
at library/core/src/slice/cmp.rs:91
91 library/core/src/slice/cmp.rs: No such file or directory.
```
>>> SRU'ed package:
GDB 12.1-0ubuntu1~22.04.1 (patched)
GCC 11.4.0-1ubuntu1~22.04
Result:
```
Breakpoint 1 at 0x4838: file associated-types.rs, line 111.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Breakpoint 1, associated_types::assoc_struct (arg=...) at
associated-types.rs:111
111 zzz(); // #break
[Inferior 1 (process 3621) exited normally]
```
Test (2) simplified C program test (test.c)
---
GDB 12.1-0ubuntu1~22.04 (unpatched)
GCC 11.4.0-1ubuntu1~22.04
Test program source:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
Commands:
```
gcc -Og -ggdb3 test.c -o test
printf "b 3\nr\nc\n" > repro
gdb --batch -x ./repro ./test
```
Result:
```
Breakpoint 1 at 0x4d8: file test.c, line 3.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Breakpoint 1, thumb_func () at test.c:3
3 return 42;
Program received signal SIGILL, Illegal instruction.
0x00401004 in ?? ()
```
Disassembly of the crash site (ARM code):
```
=> 0x004004d8 <+0>: mov r0, #42 ; 0x2a
0x004004dc <+4>: bx lr
```
Disassembly of the call site (Thumb code, +2 bytes):
```
0x004004e0 <+0>: push{r3, lr}
0x004004e2 <+2>: blx 0x4004d8
=> 0x004004e6 <+6>: pop {r3, pc}
```
>>> SRU'ed package:
GDB 12.1-0ubuntu1~22.04.1 (patched)
GCC 11.4.0-1ubuntu1~22.04
Result:
```
Breakpoint 1 at 0x4d8: file test.c, line 3.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Breakpoint 1, thumb_func () at test.c:3
3 return 42;
[Inferior 1 (process 3611) exited with code 052]
```
Conclusion
--
GDB 12.1-0ubuntu1~22.04.1 package correctly fixed the issue described in the
bug report.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2041396
Title:
gdb 12.1 generates SIGILL on armhf
Status in gdb:
Fix Released
Status in gdb package in Ubuntu:
Fix Released
Status in gdb source package in Jammy:
Fix Committed
Bug description:
[ Impact ]
* GDB 12.1 introduced a regression where it will break program execution
when the program contains mixed ARM code and THUMB code.
* Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.
[ Test Plan ]
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
GDB using the following commands ...
```
b 3
r
c
```
(you can save the contents above to a file and run GDB using `gdb -x
script ./repro`)
... you will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
[ Where problems could occur ]
* GDB is a complex software. As the patch suggests, it may break other use
cases (like single-stepping) entirely.
* Since this is an ARM-only patch, it's unlikely to affect other CPU
architectures. However, it is possible that this fix may break ARM64 execution.
[ Other Info ]
* This bug has been fixed in GDB 13, but the fix was never backported to GDB
12. You can find the upstream bug in the remote bug watch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 2041396] Re: gdb 12.1 generates SIGILL on armhf
Currently waiting for an SRU team member to process the update through
the upload queue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2041396
Title:
gdb 12.1 generates SIGILL on armhf
Status in gdb:
Fix Released
Status in gdb package in Ubuntu:
New
Status in gdb source package in Jammy:
New
Bug description:
[ Impact ]
* GDB 12.1 introduced a regression where it will break program execution
when the program contains mixed ARM code and THUMB code.
* Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.
[ Test Plan ]
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
GDB using the following commands ...
```
b 3
r
c
```
(you can save the contents above to a file and run GDB using `gdb -x
script ./repro`)
... you will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
[ Where problems could occur ]
* GDB is a complex software. As the patch suggests, it may break other use
cases (like single-stepping) entirely.
* Since this is an ARM-only patch, it's unlikely to affect other CPU
architectures. However, it is possible that this fix may break ARM64 execution.
[ Other Info ]
* This bug has been fixed in GDB 13, but the fix was never backported to GDB
12. You can find the upstream bug in the remote bug watch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2041396] Re: gdb 12.1 generates SIGILL on armhf
** Description changed:
- GDB 12.1 had a regression where it will break program execution when the
- program contains mixed ARM code and THUMB code.
+ [ Impact ]
+
+ * GDB 12.1 introduced a regression where it will break program execution
when the program contains mixed ARM code and THUMB code.
+ * Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.
+
+ [ Test Plan ]
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
- return 42;
+ return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the GDB
- using the following commands:
+ using the following commands ...
```
b 3
r
c
```
- (you can save it to a file and run GDB using `gdb -x script ./repro`)
+ (you can save the contents above to a file and run GDB using `gdb -x
+ script ./repro`)
- You will notice GDB broke the program and threw SIGILL.
+ ... you will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
- This bug has been fixed in GDB 13, but the fix was never backported to
- GDB 12. You can find the upstream bug in the remote bug watch.
+ [ Where problems could occur ]
+
+ * GDB is a complex software. As the patch suggests, it may break other use
cases (like single-stepping) entirely.
+ * Since this is an ARM-only patch, it's unlikely to affect other CPU
architectures. However, it is possible that this fix may break ARM64 execution.
+
+ [ Other Info ]
+
+ * This bug has been fixed in GDB 13, but the fix was never backported to GDB
12. You can find the upstream bug in the remote bug watch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2041396
Title:
gdb 12.1 generates SIGILL on armhf
Status in gdb:
Unknown
Status in gdb package in Ubuntu:
New
Bug description:
[ Impact ]
* GDB 12.1 introduced a regression where it will break program execution
when the program contains mixed ARM code and THUMB code.
* Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.
[ Test Plan ]
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
GDB using the following commands ...
```
b 3
r
c
```
(you can save the contents above to a file and run GDB using `gdb -x
script ./repro`)
... you will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
[ Where problems could occur ]
* GDB is a complex software. As the patch suggests, it may break other use
cases (like single-stepping) entirely.
* Since this is an ARM-only patch, it's unlikely to affect other CPU
architectures. However, it is possible that this fix may break ARM64 execution.
[ Other Info ]
* This bug has been fixed in GDB 13, but the fix was never backported to GDB
12. You can find the upstream bug in the remote bug watch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2041396] Re: gdb 12.1 generates SIGILL on armhf
I have proposed a fix in
https://code.launchpad.net/~liushuyu-011/ubuntu/+source/gdb/+git/gdb/+merge/454654.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2041396
Title:
gdb 12.1 generates SIGILL on armhf
Status in gdb:
Unknown
Status in gdb package in Ubuntu:
New
Bug description:
GDB 12.1 had a regression where it will break program execution when
the program contains mixed ARM code and THUMB code.
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
GDB using the following commands:
```
b 3
r
c
```
(you can save it to a file and run GDB using `gdb -x script ./repro`)
You will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
This bug has been fixed in GDB 13, but the fix was never backported to
GDB 12. You can find the upstream bug in the remote bug watch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2041396] [NEW] gdb 12.1 generates SIGILL on armhf
Public bug reported:
GDB 12.1 had a regression where it will break program execution when the
program contains mixed ARM code and THUMB code.
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the GDB
using the following commands:
```
b 3
r
c
```
(you can save it to a file and run GDB using `gdb -x script ./repro`)
You will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
This bug has been fixed in GDB 13, but the fix was never backported to
GDB 12. You can find the upstream bug in the remote bug watch.
** Affects: gdb
Importance: Unknown
Status: Unknown
** Affects: gdb (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Sourceware.org Bugzilla #29272
https://sourceware.org/bugzilla/show_bug.cgi?id=29272
** Also affects: gdb (Debian) via
https://sourceware.org/bugzilla/show_bug.cgi?id=29272
Importance: Unknown
Status: Unknown
** Package changed: gdb (Debian) => gdb
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2041396
Title:
gdb 12.1 generates SIGILL on armhf
Status in gdb:
Unknown
Status in gdb package in Ubuntu:
New
Bug description:
GDB 12.1 had a regression where it will break program execution when
the program contains mixed ARM code and THUMB code.
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
GDB using the following commands:
```
b 3
r
c
```
(you can save it to a file and run GDB using `gdb -x script ./repro`)
You will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
This bug has been fixed in GDB 13, but the fix was never backported to
GDB 12. You can find the upstream bug in the remote bug watch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] Re: default Chinese font is ugly
It looks like this issue mostly affects Snap apps. Please see the font config debug output attached. ** Attachment added: "font config debug output" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5665442/+files/fc-debug.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font is ugly Status in fontconfig package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
