Bug#401482: gdb: Failed to read a valid object file image from memory

2006-12-03 Thread Sam Morris
Package: gdb
Version: 6.4.90.dfsg-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

GDB always reports that it Failed to read a valid object file image from
memory when executing a program. This seems to make back traces useless
(they come out as in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400965)
and breakpoints often unworkable (they are often not triggered).

I've also noticed that gdb will often lose track of the executed process
after it catches a signal. Any attempt to examine the crashed process
results in a message such as Cannot find thread 213003: invalid thread
handle. This doesn't happen every time, however.

Maybe (hopefully!) I'm just doing something wrong, so feel free to hit
me with the cluebat... I just want gdb to work again! :)

- -- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages gdb depends on:
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libncurses5  5.5-5   Shared libraries for terminal hand
ii  libreadline5 5.2-1   GNU readline and history libraries

gdb recommends no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFc1qpshl/216gEHgRArQtAKDleZQ4PiPIzNAQ1K9dZaRG7bFLSACgx05z
BiciSf7i05kMnFJEA3BRyw0=
=igvS
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Processed: Re: Bug#401482: gdb: Failed to read a valid object file image from memory

2006-12-03 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 severity 401482 important
Bug#401482: gdb: Failed to read a valid object file image from memory
Severity set to `important' from `grave'

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#401482: gdb: Failed to read a valid object file image from memory

2006-12-03 Thread Daniel Jacobowitz
severity 401482 important
thanks

This is hardly RC.  GDB seems to work for lots of people.  I'm happy to
help with bug reports, but please don't abuse severity.

On Sun, Dec 03, 2006 at 11:15:53PM +, Sam Morris wrote:
 GDB always reports that it Failed to read a valid object file image from
 memory when executing a program. This seems to make back traces useless
 (they come out as in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400965)
 and breakpoints often unworkable (they are often not triggered).

You need to give me a recipe or a small test case demonstrating this
problem, so that I can try to reproduce it.  I suspect I won't be able
to without switching to the Debian ia32 kernels; I only run 64-bit
kernels at home.  The object file in memory is the kernel's virtual DSO
(vDSO).

-- 
Daniel Jacobowitz
CodeSourcery


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]