Activity log for bug #1171484

Date Who What changed Old value New value Message
2013-04-22 14:23:55 Nicolas Devillers bug added bug
2013-04-22 14:34:57 Nicolas Devillers description Apport crash while trying to generate a report from a gdb crash core dump. crash occure in function add_gdb_info() of file report.py on the line (around 689): if '"ERROR:' in self['GLibAssertionMessage']: The crash happens because GLibAssertionMessage as not been affected as a key in self[]. It's because apport assume that the cmd invoking gdb : "out = _command_output(gdb_cmd).decode('UTF-8', errors='replace')" will work and return correct value. In my case the gdb invokation seems to give an incomplete result starting with : "[New LWP 18326]\nwarning: Can\'t read pathname for load map: Erreur d\'entr\xe9e/sortie." ending with "No symbol table info available." therefore parts list is composed of 1 element : (pdb): len(parts) 1 (Pdb) parts[1] *** IndexError: list index out of range I guess a possible correction would be to add a check on the number on the result of the gdb invocation or on the number of items in parts list line 681. I could provide a patch but i'm not sure what is the cleanest way to correct this. Apport crash while trying to generate a report from a gdb crash core dump. crash occure in function add_gdb_info() of file report.py on the line (around 687):  if '"ERROR:' in self['GLibAssertionMessage']: The crash happens because GLibAssertionMessage as not been affected as a key in self[]. It's because apport assume that the cmd invoking gdb : "out = _command_output(gdb_cmd).decode('UTF-8', errors='replace')" will work and return correct value. In my case the gdb invokation seems to give an incomplete result starting with : "[New LWP 18326]\nwarning: Can\'t read pathname for load map: Erreur d\'entr\xe9e/sortie." ending with "No symbol table info available." therefore parts list is composed of 1 element : (pdb): len(parts) 1 (Pdb) parts[1] *** IndexError: list index out of range I guess a possible correction would be to add a check on the number on the result of the gdb invocation or on the number of items in parts list line 681. I could provide a patch but i'm not sure what is the cleanest way to correct this. affected version is apport 2.9.2
2013-04-22 14:35:11 Nicolas Devillers description Apport crash while trying to generate a report from a gdb crash core dump. crash occure in function add_gdb_info() of file report.py on the line (around 687):  if '"ERROR:' in self['GLibAssertionMessage']: The crash happens because GLibAssertionMessage as not been affected as a key in self[]. It's because apport assume that the cmd invoking gdb : "out = _command_output(gdb_cmd).decode('UTF-8', errors='replace')" will work and return correct value. In my case the gdb invokation seems to give an incomplete result starting with : "[New LWP 18326]\nwarning: Can\'t read pathname for load map: Erreur d\'entr\xe9e/sortie." ending with "No symbol table info available." therefore parts list is composed of 1 element : (pdb): len(parts) 1 (Pdb) parts[1] *** IndexError: list index out of range I guess a possible correction would be to add a check on the number on the result of the gdb invocation or on the number of items in parts list line 681. I could provide a patch but i'm not sure what is the cleanest way to correct this. affected version is apport 2.9.2 Apport crash while trying to generate a report from a gdb crash core dump. crash occure in function add_gdb_info() of file report.py on the line (around 687):  if '"ERROR:' in self['GLibAssertionMessage']: The crash happens because GLibAssertionMessage as not been affected as a key in self[]. It's because apport assume that the cmd invoking gdb : "out = _command_output(gdb_cmd).decode('UTF-8', errors='replace')" will work and return correct value. In my case the gdb invokation seems to give an incomplete result starting with : "[New LWP 18326]\nwarning: Can\'t read pathname for load map: Erreur d\'entr\xe9e/sortie." ending with "No symbol table info available." therefore parts list is composed of 1 element : (pdb): len(parts) 1 (Pdb) parts[1] *** IndexError: list index out of range I guess a possible correction would be to add a check on the number on the result of the gdb invocation or on the number of items in parts list line 681. I could provide a patch but i'm not sure what is the cleanest way to correct this. Affected version is apport 2.9.2.
2013-04-24 22:53:09 Nicolas Devillers description Apport crash while trying to generate a report from a gdb crash core dump. crash occure in function add_gdb_info() of file report.py on the line (around 687):  if '"ERROR:' in self['GLibAssertionMessage']: The crash happens because GLibAssertionMessage as not been affected as a key in self[]. It's because apport assume that the cmd invoking gdb : "out = _command_output(gdb_cmd).decode('UTF-8', errors='replace')" will work and return correct value. In my case the gdb invokation seems to give an incomplete result starting with : "[New LWP 18326]\nwarning: Can\'t read pathname for load map: Erreur d\'entr\xe9e/sortie." ending with "No symbol table info available." therefore parts list is composed of 1 element : (pdb): len(parts) 1 (Pdb) parts[1] *** IndexError: list index out of range I guess a possible correction would be to add a check on the number on the result of the gdb invocation or on the number of items in parts list line 681. I could provide a patch but i'm not sure what is the cleanest way to correct this. Affected version is apport 2.9.2. Apport crash while trying to generate a report from a gdb crash core dump. crash occure in function add_gdb_info() of file report.py on the line (around 687):  if '"ERROR:' in self['GLibAssertionMessage']: The crash happens because GLibAssertionMessage as not been affected as a key in self[]. It's because apport assume that the cmd invoking gdb : "out = _command_output(gdb_cmd).decode('UTF-8', errors='replace')" will work and return correct value. In my case the gdb invokation seems to give an incomplete result starting with : "[New LWP 18326]\nwarning: Can\'t read pathname for load map: Erreur d\'entr\xe9e/sortie." ending with "No symbol table info available." therefore parts list is composed of 1 element : (pdb): len(parts) 1 (Pdb) parts[1] *** IndexError: list index out of range I guess a possible correction would be to add a check on the result of the gdb invocation or on the number of items in parts list line 681. I could provide a patch but i'm not sure what is the cleanest way to correct this. Affected version is apport 2.9.2.
2013-05-21 12:38:33 Martin Pitt affects apport apport (Ubuntu)
2013-05-21 12:38:35 Launchpad Janitor branch linked lp:apport
2013-05-21 12:38:49 Martin Pitt apport (Ubuntu): status New Fix Committed
2013-05-22 11:10:22 Launchpad Janitor apport (Ubuntu): status Fix Committed Fix Released
2013-05-29 13:58:54 Nicolas Devillers apport (Ubuntu): status Fix Released New
2013-07-03 17:05:45 Nicolas Devillers attachment added _usr_bin_watch.1000.crash https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1171484/+attachment/3723288/+files/_usr_bin_watch.1000.crash
2013-07-23 13:53:50 Nicolas Devillers summary Apport crash while generating report from a gdb crash Apport crash while adding gdb_info to report when gdb couldn't load symbol map
2013-07-23 15:11:48 Nicolas Devillers attachment added if gdb output contains "no symbol table info available" we don't parse it https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1171484/+attachment/3746607/+files/patch_add_gdb_report.txt
2013-07-23 16:17:27 Ubuntu Foundations Team Bug Bot tags gdb report gdb patch report
2013-07-23 16:17:35 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Review Team
2013-08-01 16:07:09 Brian Murray apport (Ubuntu): assignee Martin Pitt (pitti)
2013-08-01 16:07:14 Brian Murray bug added subscriber Brian Murray
2013-08-02 06:58:45 Martin Pitt apport (Ubuntu): status New Fix Committed
2013-08-02 15:35:21 Launchpad Janitor apport (Ubuntu): status Fix Committed Fix Released