mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Filipau, Ihar" <ifilipau@sussdd.de>
To: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: gdb on 2.2/2.4
Date: Thu, 10 Apr 2003 14:52:35 +0100	[thread overview]
Message-ID: <7A5D4FEED80CD61192F2001083FC1CF9065167@CHARLY> (raw)

Hello!

  [ CC me please - I'm not subscribed ]

  Couple of issues. I hope RH8 kernels not much /patched/ 
  comparing to vanilla in this respect.

  1. gdb doesn't work on 2.4 - if app got SIGSEGV - I cannot see
     backtrace of random thread. I have mutli-threaded app - but 
     gdb cannot access any other thread - only main thread.

  2. on 2.4 + ptrace() security fix, gdb on signal prints error 
     message: "Couldn't access registers: permission denied".
     and sure only 'quit' works correctly after this.

  In both cases it is run from user account.

  Does any-one has any clue how to make gdb working on rh8?
  I have tried to use vanilla kernel - but have no succes to 
  date...

  I'm not much about debugging - but finding a 
  SIGSEGV/SIGILL source is much more faster with gdb.

P.S. System: SMP/PIII (Tried in both smp/nosmp), RH8 std kernel, 
     RH8 updated kernel, 2.4.20. gcc 3.2/3.2.2, gdb 5.3.

--- Regards&Wishes! With respect  Ihar "Philips" Filipau, and Phil for
friends

- - - - - - - - - - - - - - - - - - - - - - - - -
MCS/Mathematician - System Programmer
Ihar Filipau 
Software entwickler @ SUSS MicroTec Test Systems GmbH, 
Suss-Strasse 1, D-01561 Sacka (bei Dresden)
e-mail: ifilipau@sussdd.de  tel: +49-(0)-352-4073-327
fax: +49-(0)-352-4073-700   web: http://www.suss.com/

                 reply	other threads:[~2003-04-10 12:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7A5D4FEED80CD61192F2001083FC1CF9065167@CHARLY \
    --to=ifilipau@sussdd.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®