From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Tromey To: Eli Zaretskii Cc: gdb@sources.redhat.com, bug-gnu-emacs@gnu.org Subject: Re: Using gdb with emacs Date: Mon, 10 Sep 2001 19:58:00 -0000 Message-id: <87wv36mnfy.fsf@creche.redhat.com> References: <874rqfvl52.fsf@creche.redhat.com> <2593-Fri07Sep2001105921+0300-eliz@is.elta.co.il> <87elpid9dt.fsf@creche.redhat.com> <7458-Sat08Sep2001103423+0300-eliz@is.elta.co.il> X-SW-Source: 2001-09/msg00096.html >>>>> "Eli" == Eli Zaretskii writes: Eli> It can't. I didn't assume you have many files with the same Eli> basename. The problem doesn't really occur if every file has a unique name, due to how the gdb `break' command searches for files. Eli> (gdb) break ../mauve/gnu/testlet/java/text/DateFormat/Test.java:85 Eli> and it would have worked, right? Yes, that would have worked. Eli> What you, in effect, want is for GUD to support relative file Eli> names which are not relative to the default directory of the Eli> buffer from which you set the breakpoint. Actually, that isn't what I want. I want it to work without any extra interaction by me. One way would be for both gdb and Emacs to agree that using absolute paths will work. Eli> AFAIK, there's no easy way this information can come from GDB Eli> itself, so we should probably burden the user with supplying it. I dislike this solution. It means more work for me, the user, when clearly more work isn't required -- Emacs knows the absolute path, and gdb can (in theory) already find it via the paths specified to `dir'. For instance, gdb already knows that `../mauve/gnu/testlet/java/text/DateFormat/Test.java' is a file in my program. It gets this information, verbatim, from the debug info. If I type `break /blah/blah/mauve/gnu/testlet/java/text/DateFormat/Test.java:57', gdb could very easily go down the list of directories as set by `dir', and for each one go through each file in the executable, concatenate and normalize, and then see if the answer is right. For instance, if the directory list is `/one:/blah/blah, then gdb could first try: /one/../mauve/gnu/testlet/java/text/DateFormat/Test.java which normalizes to (I assume no symlinks, but gdb need not -- it could use realpath): /one/mauve/gnu/testlet/java/text/DateFormat/Test.java If that fails then gdb would try: /blah/blah/../mauve/gnu/testlet/java/text/DateFormat/Test.java which normalizes to: /blah/blah/mauve/gnu/testlet/java/text/DateFormat/Test.java -- the right answer. This might be expensive, so probably it should only be done if the argument to `break' is an absolute path. Or maybe caching would be appropriate. One reason I think this is important is that even the worst IDE can let the user do this without a lot of fuss. I think it shouldn't be a problem for Emacs+gdb to handle it too. Tom