From: "André Pönitz" <andre.poenitz@nokia.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch gdb]: Fix some DOS-path related issues in gdb
Date: Fri, 04 Mar 2011 13:05:00 -0000 [thread overview]
Message-ID: <201103041411.34582.andre.poenitz@nokia.com> (raw)
In-Reply-To: <20110304051203.GA30306@adacore.com>
On Friday 04 March 2011 06:12:03 ext Joel Brobecker wrote:
> > Is that use-case even practical? Who would develop on Windows if they
> > have Linux or Irix?
>
> I really can't say that this is going to happen frequently...
> But I've seen situations where developers cross compile from
> their Windows desktop and then execute on a server running a Unix-like
> system. It might make less sense for GNU/Linux (I think that people
> are less scared of it, these days), but could make more sense for
> IRIX - I don't know how easy it is to procure a machine running
> IRIX these days...
Just two data points from an "gdb frontend" perspective:
- Two weeks ago I had to enable core file handling on Windows which I
previously disabled because I assumed it would not be needed.
Someone was actually trying to use it. Quote from the bug report:
(http://bugreports.qt.nokia.com/browse/QTCREATORBUG-3813)
"I want to use gdb (compiled using Mingw for mips64 target) to
debug a machine that dumps core."
- Today(!) I got a log file containing
[...]
GNU gdb (GDB) 7.2
This GDB was configured as "i686-pc-mingw32".
[...]
153-break-insert -f "\"main.cpp\":47"
153^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",
addr="0x004013b8",func="qMain(int, char **)",file="..\\calendar\\main.cpp",
fullname="C:\\SDK1\\Examples\\4.7\\richtext\\calendar-build-desktop/..\\calendar\\main.cpp",
line="47",times="0",original-location="\"main.cpp\":47"}
[...]
Note the "/.." bit in fullname.
People try to use gdb in a lot of "cross debugging" scenarios nowadays.
Andre'
next prev parent reply other threads:[~2011-03-04 13:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=QoOiBg3XmMv+hRNe8DkT2YiVGZ=7NhaQwzCey@mail.gmail.com>
2011-03-03 12:10 ` Kai Tietz
2011-03-03 13:24 ` Eli Zaretskii
2011-03-03 13:48 ` Kai Tietz
2011-03-03 14:00 ` Eli Zaretskii
2011-03-03 14:58 ` Joel Brobecker
2011-03-03 15:25 ` Kai Tietz
2011-03-03 15:32 ` Pedro Alves
2011-03-03 15:41 ` Kai Tietz
2011-03-03 16:09 ` Pedro Alves
2011-03-03 16:19 ` Kai Tietz
2011-03-03 16:42 ` Pedro Alves
2011-03-03 17:32 ` Kai Tietz
2011-03-04 7:23 ` Vladimir Simonov
2011-03-04 8:23 ` Joel Brobecker
2011-03-07 19:28 ` Jan Kratochvil
2011-03-07 19:28 ` Pedro Alves
2011-03-07 19:34 ` Jan Kratochvil
2011-03-03 18:09 ` Eli Zaretskii
2011-03-04 5:12 ` Joel Brobecker
2011-03-04 13:05 ` André Pönitz [this message]
2011-03-04 9:48 ` Kai Tietz
2011-03-04 10:37 ` Mark Kettenis
2011-03-05 9:13 ` Kai Tietz
2011-03-05 11:38 ` Vladimir Simonov
2011-03-05 12:45 ` Kai Tietz
2011-03-23 11:16 ` Kai Tietz
2011-03-23 12:44 ` Mark Kettenis
2011-03-23 14:07 ` Kai Tietz
2011-03-23 14:16 ` Pedro Alves
2011-03-23 14:18 ` Kai Tietz
2011-03-23 14:29 ` Pierre Muller
[not found] ` <-544184502231544940@unknownmsgid>
2011-03-23 14:44 ` Kai Tietz
2011-03-23 15:29 ` Pedro Alves
2011-03-23 15:29 ` Kai Tietz
2011-03-23 18:24 ` Eli Zaretskii
2011-03-23 21:11 ` Kai Tietz
2011-03-03 17:02 ` Mark Kettenis
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=201103041411.34582.andre.poenitz@nokia.com \
--to=andre.poenitz@nokia.com \
--cc=gdb-patches@sourceware.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