Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@wins.uva.nl>
To: j_clifton@aerosimulation.com
Cc: gdb@sourceware.cygnus.com
Subject: Re: More mmap/Linux questions
Date: Thu, 31 Aug 2000 13:23:00 -0000	[thread overview]
Message-ID: <200008312022.e7VKM5S00361@delius.kettenis.local> (raw)
In-Reply-To: <0008319677.AA967740722@mailserver.aerosimulation.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

   Date: Thu, 31 Aug 2000 12:52:02 -0400
   From: <j_clifton@aerosimulation.com>

   Can someone familiar with the Linux Kernel (2.2 or higher) explain this in more
   detail. Can I patch the kernel to get rid of this behaviour?

You'll probably have more success asking your question on the
linux-kernel mailing list (linux-kernel@kernel.org).

Mark
From olivier.isnard@ipsn.fr Fri Sep 01 02:32:00 2000
From: ISNARD Olivier 132311 <olivier.isnard@ipsn.fr>
To: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: Q: using gdb and lahey compiler
Date: Fri, 01 Sep 2000 02:32:00 -0000
Message-id: <FEC064C12976D31197DA00A0C9E93C90760ED3@ALGER>
X-SW-Source: 2000-09/msg00000.html
Content-length: 445

Hi all !

For some reason I have to use the Lahey fortran 90 compiler and I wonder if
it is possible to debug
such a generated program with gdb. I'm also using cygwin (NT pc).




____________

Dr. Olivier Isnard
IPSN
Département de Prévention et d'Etudes des Accidents
Service d'Etudes des Situations de Crises et d'Informatique
BP 6 - 92265 FONTENAY AUX ROSES Cedex
Tel  : 01 46 54 73 85
Fax : 01 46 54 90 40
Email : Olivier.Isnard@Ipsn.fr


      reply	other threads:[~2000-08-31 13:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-31  9:52 j_clifton
2000-08-31 13:23 ` Mark Kettenis [this message]

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=200008312022.e7VKM5S00361@delius.kettenis.local \
    --to=kettenis@wins.uva.nl \
    --cc=gdb@sourceware.cygnus.com \
    --cc=j_clifton@aerosimulation.com \
    /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