[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#506850: marked as done (libc6-prof: profiling C library causes FPE)



Your message dated Sat, 02 Nov 2013 12:41:11 +0100
with message-id <5274E4D7.9060102@debian.org>
and subject line Re: Processed: fixed 212547 in 1:9.4.1-P1-2, notfound 325165 in 1.3.3-1, fixed 326413 in 0.3.2 ..., reopening 328306 ...
has caused the Debian Bug report #506850,
regarding libc6-prof: profiling C library causes FPE
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
506850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506850
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-prof
Version: 2.7-16
Severity: normal

Executables linked with option -p or -pg and profiling library libc_p.a
throw a SIGFPE.  Even very simple one as this:

% cat x.c
#include <stdio.h>
main(){printf("hello, world!\n");}

will die:

% gcc -p x.c -lc_p
% a.out
[1]    30461 floating point exception (core dumped)  a.out
% gcc -pg x.c -lc_p
% a.out
[1]    30468 floating point exception (core dumped)  a.out
% gcc -g -pg x.c -lc_p
% gdb a.out
GNU gdb 6.8-debian
This GDB was configured as "i486-linux-gnu"...
(gdb) r
Starting program: /home/xxx/a.out

Program received signal SIGFPE, Arithmetic exception.
0x08056c86 in profil ()
Current language:  auto; currently asm
(gdb) bt
#0  0x08056c86 in profil ()
#1  0x08056968 in moncontrol ()
#2  0x0804d136 in __gmon_start__ () at gmon-start.c:74
#3  0xb7f3da22 in ?? () from /lib/libgcc_s.so.1
#4  0xb7f5bbe8 in ?? ()
#5  0xb7f77ff4 in ?? () from /lib/ld-linux.so.2
#6  0xbfe76068 in ?? ()
#7  0xb7f6ade4 in ?? () from /lib/ld-linux.so.2
#8  0x00000001 in ?? ()
#9  0xbfe760c4 in ?? ()
#10 0xbfe760cc in ?? ()
#11 0x00000009 in ?? ()
#12 0xbfe7607c in ?? ()
#13 0x00000001 in ?? ()
#14 0x08048034 in ?? ()

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libc6-prof depends on:
ii  libc6                         2.7-16     GNU C Library: Shared libraries

libc6-prof recommends no packages.

libc6-prof suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
On 2013-11-02 09:30, Aurelien Jarno wrote:
> On Fri, Nov 01, 2013 at 10:34:06PM +0000, Debian Bug Tracking System wrote:
>>> found 506850 2.10.1-3
>> Bug #506850 {Done: Aurelien Jarno <aurelien@aurel32.net>} [libc6-prof] libc6-prof: profiling C library causes FPE
>> Marked as found in versions eglibc/2.10.1-3 and reopened.
>>> notfixed 506850 2.7-11
>> Bug #506850 [libc6-prof] libc6-prof: profiling C library causes FPE
>> No longer marked as fixed in versions 2.7-11.
> 
> You have reopened this bug. Could you please provide me more information
> about the problem? I am still unable to reproduce the problem building
> code with profiling enable as described in
> /usr/share/doc/libc6-prof/README.Debian.

Not sure what happened here. I only planned to fix up the fixed/found
versions so that this ancient bug could be archived eventually ...


Andreas

--- End Message ---

Reply to: