[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

[Sebastien Bacher]

** Changed in: glib2.0 (Ubuntu)
 Assignee: nassim (moujane) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  Fix Released
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Released
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [Impact]
  apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.

  [Test Case]
  Run the autopkgtest and observe the failure.
  With the version of the package in proposed the test will not be run.

  [Regression Potential]
  We are just disabling a broken test so there is none.

  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

[nassim]

** Changed in: glib2.0 (Ubuntu)
 Assignee: (unassigned) => nassim (moujane)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  Fix Released
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Released
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [Impact]
  apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.

  [Test Case]
  Run the autopkgtest and observe the failure.
  With the version of the package in proposed the test will not be run.

  [Regression Potential]
  We are just disabling a broken test so there is none.

  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.3-0ubuntu8.3

---
apport (2.20.3-0ubuntu8.3) yakkety; urgency=medium

  * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues
with apt key ring. Thanks to Dimitri John Ledkov for the patch.
(LP: #1651623)
  * Disable report.test_add_gdb_info_abort_glib test case for now, as the
glib assertion message is broken under current Ubuntu (LP: #1689344)
  * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in
every report. (LP: #1673557)

 -- Brian Murray   Wed, 10 May 2017 18:10:32 -0700

** Changed in: apport (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  Fix Released
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Released
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [Impact]
  apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.

  [Test Case]
  Run the autopkgtest and observe the failure.
  With the version of the package in proposed the test will not be run.

  [Regression Potential]
  We are just disabling a broken test so there is none.

  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.4-0ubuntu4.1

---
apport (2.20.4-0ubuntu4.1) zesty; urgency=medium

  * Disable report.test_add_gdb_info_abort_glib test case for now, as the
glib assertion message is broken under current Ubuntu (LP: #1689344)
  * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues
with apt key ring. Thanks to Dimitri John Ledkov for the patch.
(LP: #1651623)

 -- Brian Murray   Wed, 10 May 2017 17:05:11 -0700

** Changed in: apport (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  Fix Committed
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Released
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [Impact]
  apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.

  [Test Case]
  Run the autopkgtest and observe the failure.
  With the version of the package in proposed the test will not be run.

  [Regression Potential]
  We are just disabling a broken test so there is none.

  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

[Brian Murray]

Verification for yakkety:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-
yakkety/yakkety/amd64/a/apport/20170512_193229_92825@/log.gz

Verification for zesty:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/amd64/a/apport/20170512_193953_7d1ed@/log.gz

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  Fix Committed
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Committed
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [Impact]
  apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.

  [Test Case]
  Run the autopkgtest and observe the failure.
  With the version of the package in proposed the test will not be run.

  [Regression Potential]
  We are just disabling a broken test so there is none.

  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

[Łukasz Zemczak]

Hello Brian, or anyone else affected,

Accepted apport into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.3-0ubuntu8.3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apport (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  Fix Committed
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Committed
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [Impact]
  apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.

  [Test Case]
  Run the autopkgtest and observe the failure.
  With the version of the package in proposed the test will not be run.

  [Regression Potential]
  We are just disabling a broken test so there is none.

  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

[Łukasz Zemczak]

Hello Brian, or anyone else affected,

Accepted apport into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.4-0ubuntu4.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apport (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  In Progress
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Committed
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [Impact]
  apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.

  [Test Case]
  Run the autopkgtest and observe the failure.
  With the version of the package in proposed the test will not be run.

  [Regression Potential]
  We are just disabling a broken test so there is none.

  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

[Brian Murray]

** Description changed:

+ [Impact]
+ apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.
+ 
+ [Test Case]
+ Run the autopkgtest and observe the failure.
+ With the version of the package in proposed the test will not be run.
+ 
+ [Regression Potential]
+ We are just disabling a broken test so there is none.
+ 
  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.
  
  With the generated binary, it used to return the following:
  
  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 < 0)"
  
  However, now I am seeing:
  
- (gdb) print __glib_assert_msg 
+ (gdb) print __glib_assert_msg
  $1 = 1332592064
- (gdb) print (char*) __glib_assert_msg 
+ (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 
  
  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  In Progress
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  In Progress
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [Impact]
  apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.

  [Test Case]
  Run the autopkgtest and observe the failure.
  With the version of the package in proposed the test will not be run.

  [Regression Potential]
  We are just disabling a broken test so there is none.

  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

[Brian Murray]

** Changed in: apport (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: apport (Ubuntu Yakkety)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: apport (Ubuntu Zesty)
 Assignee: (unassigned) => Brian Murray (brian-murray)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  In Progress
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  In Progress
Status in glib2.0 source package in Zesty:
  New

Bug description:
  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg 
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg 
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

[Brian Murray]

** Also affects: glib2.0 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: apport (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: apport (Ubuntu Zesty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  New
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  New
Status in glib2.0 source package in Zesty:
  New

Bug description:
  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg 
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg 
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1689344] Re: print of __glib_assert_msg not returning a message

[Brian Murray]

I tested the yakkety core file and binary with a xenial version of gdb
and didn't still received the cannot access memory error, so I don't
think its a gdb bug.

** Package changed: gdb (Ubuntu) => glib2.0 (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New

Bug description:
  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg 
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg 
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp