* That dwarf2read patch i just submitted
@ 2000-10-23 7:02 Daniel Berlin
[not found] ` <1001023165317.ZM12542@ocotillo.lan>
0 siblings, 1 reply; 4+ messages in thread
From: Daniel Berlin @ 2000-10-23 7:02 UTC (permalink / raw)
To: gdb-patches
So no one feels slighted, that last dwarf2 patch I submitted (to add
support for .debug_loc) is based on a patch I found on gdb-patches
that is a few years old, submitted originally by one of the ADA guys.
I cleaned it up so that it works with dwarf2read of today, but if you
want credit, email me, and i'll put your name in the ChangeLog
instead.
--Dan
^ permalink raw reply [flat|nested] 4+ messages in thread[parent not found: <1001023165317.ZM12542@ocotillo.lan>]
[parent not found: <m3aebvqyxy.fsf@dan2.cygnus.com>]
* Re: That dwarf2read patch i just submitted [not found] ` <m3aebvqyxy.fsf@dan2.cygnus.com> @ 2000-10-23 10:32 ` Kevin Buettner [not found] ` <m3d7grpa35.fsf@dan2.cygnus.com> [not found] ` <39F60D7B.C901357F@apple.com> 0 siblings, 2 replies; 4+ messages in thread From: Kevin Buettner @ 2000-10-23 10:32 UTC (permalink / raw) To: Daniel Berlin; +Cc: gdb-patches On Oct 23, 12:55pm, Daniel Berlin wrote: > Kevin Buettner <kevinb@cygnus.com> writes: > > > On Oct 23, 10:02am, Daniel Berlin wrote: > > > > > So no one feels slighted, that last dwarf2 patch I submitted (to add > > > support for .debug_loc) is based on a patch I found on gdb-patches > > > that is a few years old, submitted originally by one of the ADA guys. > > > I cleaned it up so that it works with dwarf2read of today, but if you > > > want credit, email me, and i'll put your name in the ChangeLog > > > instead. > > > > Dan, > > > > You should definitely give credit to the original submitter of the > > patch (whether they step forward or not). Also, you should make sure > > that we have a copyright assignment on file for whomever submitted > > that patch. > > The problem is I can't seem to find it in the archives anymore using > the search engine, or else I would have. I really don't want to go > back month by month, trying to find the patch again. It looks to me like it was http://sources.redhat.com/ml/gdb-patches/1999-q2/msg00054.html The author of this patch is Brian Nettleton. > The patch is actually <30 lines of code, and thus, shouldn't require > copyright assignment. I'm not sure what the metric is for requiring a copyright assignment, but I thought it was lower than 30. (Perhaps Andrew could let us know?) Anyway, you're off by an order of magnitude. If I'm looking at the right patch, it's actually 322 lines long. The number of lines affected by this patch is also greater than 30. The locblock function and corresponding comment alone are 39 lines. > I also modified every line of the patch, literally. It is true that you modified many of the lines, but you didn't touch *all* of them. E.g, with the exception of the comment (which you split to be on two lines), the following section from Brian's patch appears to be identical to what you submitted: + { + char *loc_ptr; + struct dwarf_block *result; + + switch (attr->form) + { + case DW_FORM_block: + case DW_FORM_block1: + case DW_FORM_block2: + case DW_FORM_block4: + return DW_BLOCK(attr); + case DW_FORM_ref_addr: + case DW_FORM_ref_udata: + /* return the first block in the location list for now */ + loc_ptr = dwarf_loc_buffer + dwarf2_get_ref_die_offset(attr); Even if you had modified every line from Brian's patch, he should still be credited for the changes. It's a maintainer's job to adapt a patch so that it works with current sources. Adapting a patch that is several years old may well require substantial modification, but the original submitter should still be given credit. (And if he's to be given credit, we must then observe the FSF's mandates regarding copyright assignments.) Kevin From ac131313@cygnus.com Mon Oct 23 10:59:00 2000 From: Andrew Cagney <ac131313@cygnus.com> To: David B Anderson <davea@quasar.engr.sgi.com> Cc: gdb-patches@sourceware.cygnus.com Subject: Re: spelling corrections: request approval Date: Mon, 23 Oct 2000 10:59:00 -0000 Message-id: <39F47B09.1F8A7C23@cygnus.com> References: <200010141539.IAA32359@quasar.engr.sgi.com> X-SW-Source: 2000-10/msg00151.html Content-length: 757 David B Anderson wrote: > > Requesting approval for checkin of the following > spelling corrections in comments. > > My last request had too many different maintainers > in one spelling correction list, so no one person wanted > to approve it (is my interpretation/guess). > And, too, the set of corrections was, well, large. > > So I'm trying to break this down sensibly into separate > requests. Rather than require that you get approval for each of these cleanups, I see no reason why you shouldn't follow the strategy that KevinB has adopted for PARAMS. Post the RFA/RFC for the cleanups and then, a day or so later, just commit the patch. Baring the occasional *colourful* comment, I can't see any problems :-) thanks for doing this, Andrew From msnyder@redhat.com Mon Oct 23 11:03:00 2000 From: Michael Snyder <msnyder@redhat.com> To: josef ezra <jezra@emc.com> Cc: gdb-patches@sourceware.cygnus.com Subject: Re: tracepoints implementation: bug in byte code generating. Date: Mon, 23 Oct 2000 11:03:00 -0000 Message-id: <39F47D62.2B5B@redhat.com> References: <00c801c02c9a$fe671c90$6c219fa8@lss.emc.com> <39D8D1CE.3059@redhat.com> <004e01c039d8$774c1d50$6c219fa8@lss.emc.com> <39EF3020.3F6A@redhat.com> <005b01c039f6$f46b1390$6c219fa8@lss.emc.com> <39EF381C.7EE6@redhat.com> <006101c039f9$df09df60$6c219fa8@lss.emc.com> <5mvguo5spm.fsf@jtc.redback.com> <008501c03aad$46c9d700$6c219fa8@lss.emc.com> <39F090F3.2DDC@redhat.com> <009001c03adb$b46a7b60$6c219fa8@lss.emc.com> <39F0BF1B.74DD@redhat.com> <003d01c03b0e$42568040$961919ac@lss.emc.com> X-SW-Source: 2000-10/msg00152.html Content-length: 5987 > > > Since this discussion now involves only tracepoints, > > after this reply I will continue it in private email > > unies someone on the list pipes up and expresses an > > interest in keeping it public. OK with you Josef? > > Putting gdb-patches back IN the Cc: list, at one reader's request. Oh well... ;-) > > Josef Ezra wrote: > > > > > > Let me try to list the features that I would like to have, if you think > that > > > other tracepoints clients may be interested, I will be more then happy > to > > > cooperate. > > > > > > -In actions: > > > -- Trace/ref different memory ranges. > > > > Not sure what you mean by the above. > > As I mentioned before, our target is working with two memory spaces: regular > and shared. It is very common to have a pointer in regular memory that > points to a structure in shared memory which one of it's field is a pointer > to different structure in shared memory which I would like to trace. > Something like: > - Special-trace (from other memory space) X bytes in offset Y from: > - Special-trace-ref (size is pointer size) in offset Z from: > - My-regular-memory-pointer If we add support for separate memory spaces to GDB, then I would favor adding it to the traceing syntax as well. Otherwise not. I don't want to start throwing a bunch of stuff into trace that would only be supported on this target or that one. And if GDB can't support multi-address-spaces, then you wouldn't have a standard way to display your results. The whole strength of the tracing implementation, in my opinion, is that it uses the same expression syntax as the rest of GDB. Therefore whatever data you collect can be used by the rest of GDB without modification. > > > -- Stop all traces on condition. > > > > That would be useful, sure. > > > > > -- Save back trace functions chain. (I can't save all the stack, > > > but I can save a limited array of function addresses) > > > > Tracepoints can already do that. I do it regularly in demos. > > All you need to do is define a memory range relative to the > > stack pointer register. Capture all that memory, and you can > > do backtraces, examine the local variables of your caller, > > and pretty much everything else you would expect. > > > This might me perfect for most targets, but in our environment there are big > stack gaps every time C function is calling assembly function and vice > versa. Dedicating most of the trace buffer to save the stack, I can't back > trace more then two or three functions. I considered that as a way to > compress backtrace data (paying the price of losing information). Then just collect two chunks of memory instead of one. Trace can already do that, it doesn't need a special extension. If we start putting in everybody's idea of an extension that benefits only one target, we're gonna end up with a mess. There's always gonna be a limit to how much stack you can collect. You only have so much room in your collection buffer. If you want to be able to trace back more than a few stack levels, it will of course cost you, no matter what kind of standard or non-standard stack you have. > > > -In output: > > > --Show/set memory from different memory space - (already suggested by > J.T.C) > > > > Fine, but not related to traceipoints. > > > > > --Display (if traced) the functions backtrace array. > > > > Can already do that. See above. > > > > > -I also need a user interface for conditional trace commands. The Stub > > > specification has provisions for aop_goto but I could not find a way to > > > access this through GDB. > > > > If you mean something like: > > if (a == b) then collect c > > yes, we'd like to have that. > > > > If you mean something like > > if (a == b) then activate tracepoint N > > then yes, we'd like to have that too. > > Well, I had meant the first 'cause it can be done with the existing byte > code, but having the other one could be nice too. > > > > > > -As a reply to "QT_Frame" I would like to get the passcount with the > frame > > > > Hitcount, I assume you mean. Passcount is something different. > > Yes, I'm sure we'd like that too. > > > > With all of these, however, we would have to talk about > > the syntax for the remote protocol. We would not want > > new syntax to break old existing stubs or debuggers. > > > > > and tracepoint numbers. > > > > Mmmmm... do we need that? The frame info ALWAYS contains > > the PC, and the PC would generally uniquely identify a > > tracepoint. > > > > I guess I haven't thought enough about this one. How a different probed able > command that will return list of tracepoints with their hitcounts? Would it > be too noisy? You can do that now, I think. Well, you could, if you just had the hitcounts. It's just a matter of processing the data once you get it. You can either write gdb scripts or tcl/tk code to produce whatever kind of report or display you want. > > > -In the future I will like to have a trace/ref of long address with > > > base-offset parameters. > > > > Have to explain to me what you mean. > > Oh', it is just a special-trace-64-bits and special-trace-ref-64-bits > commands for letting the target know it has to use bigger address. (in my > case it means the target should pop two items from the stack instead of > one). At the gdb side the user should be able to determine separately the > base and the offset address. I don't understand -- is this another reference to your separate address spaces? If the target architecture supports long pointers and short pointers, then GDB should already know about that (although I can't think of an architecture for which this is true.) I think you need to make this concept into something that can be supported in the C expression language. Trace should support anything that can be expressed as a C expression. > > > thanks for your comments - Josef Ezra > > > > No problem. Happy that someone else is working on it. > > > > Michael > > > Josef From jezra@emc.com Mon Oct 23 13:00:00 2000 From: "Josef Ezra" <jezra@emc.com> To: "Michael Snyder" <msnyder@redhat.com> Cc: <gdb-patches@sourceware.cygnus.com>, <shagam@emc.com>, <sgordon@emc.com> Subject: Re: tracepoints implementation: bug in byte code generating. Date: Mon, 23 Oct 2000 13:00:00 -0000 Message-id: <004001c03d2c$14209970$6c219fa8@lss.emc.com> References: <00c801c02c9a$fe671c90$6c219fa8@lss.emc.com> <39D8D1CE.3059@redhat.com> <004e01c039d8$774c1d50$6c219fa8@lss.emc.com> <39EF3020.3F6A@redhat.com> <005b01c039f6$f46b1390$6c219fa8@lss.emc.com> <39EF381C.7EE6@redhat.com> <006101c039f9$df09df60$6c219fa8@lss.emc.com> <5mvguo5spm.fsf@jtc.redback.com> <008501c03aad$46c9d700$6c219fa8@lss.emc.com> <39F090F3.2DDC@redhat.com> <009001c03adb$b46a7b60$6c219fa8@lss.emc.com> <39F0BF1B.74DD@redhat.com> <003d01c03b0e$42568040$961919ac@lss.emc.com> <39F47D62.2B5B@redhat.com> X-SW-Source: 2000-10/msg00153.html Content-length: 5934 > > > > -In actions: > > > > -- Trace/ref different memory ranges. > > > > > > Not sure what you mean by the above. > > > > As I mentioned before, our target is working with two memory spaces: regular > > and shared. It is very common to have a pointer in regular memory that > > points to a structure in shared memory which one of it's field is a pointer > > to different structure in shared memory which I would like to trace. > > Something like: > > - Special-trace (from other memory space) X bytes in offset Y from: > > - Special-trace-ref (size is pointer size) in offset Z from: > > - My-regular-memory-pointer > > If we add support for separate memory spaces to GDB, > then I would favor adding it to the traceing syntax > as well. Otherwise not. I don't want to start throwing > a bunch of stuff into trace that would only be supported > on this target or that one. And if GDB can't support > multi-address-spaces, then you wouldn't have a standard > way to display your results. > > The whole strength of the tracing implementation, > in my opinion, is that it uses the same expression > syntax as the rest of GDB. Therefore whatever data > you collect can be used by the rest of GDB without > modification. > What is the appropriate generic interface to trace and show other memory spaces? I can use a good advice here. > > > > -- Stop all traces on condition. > > > > > > That would be useful, sure. > > > > > > > -- Save back trace functions chain. (I can't save all the stack, > > > > but I can save a limited array of function addresses) > > > > > > Tracepoints can already do that. I do it regularly in demos. > > > All you need to do is define a memory range relative to the > > > stack pointer register. Capture all that memory, and you can > > > do backtraces, examine the local variables of your caller, > > > and pretty much everything else you would expect. > > > > > This might me perfect for most targets, but in our environment there are big > > stack gaps every time C function is calling assembly function and vice > > versa. Dedicating most of the trace buffer to save the stack, I can't back > > trace more then two or three functions. I considered that as a way to > > compress backtrace data (paying the price of losing information). > > Then just collect two chunks of memory instead of one. > Trace can already do that, it doesn't need a special > extension. If we start putting in everybody's idea > of an extension that benefits only one target, we're > gonna end up with a mess. > > There's always gonna be a limit to how much stack you can > collect. You only have so much room in your collection > buffer. If you want to be able to trace back more than > a few stack levels, it will of course cost you, no matter > what kind of standard or non-standard stack you have. > I withdraw this suggestion. > > > > -In output: > > > > --Show/set memory from different memory space - (already suggested by > > J.T.C) > > > > > > Fine, but not related to traceipoints. > > > > > > > --Display (if traced) the functions backtrace array. > > > > > > Can already do that. See above. > > > > > > > -I also need a user interface for conditional trace commands. The Stub > > > > specification has provisions for aop_goto but I could not find a way to > > > > access this through GDB. > > > > > > If you mean something like: > > > if (a == b) then collect c > > > yes, we'd like to have that. > > > > > > If you mean something like > > > if (a == b) then activate tracepoint N > > > then yes, we'd like to have that too. > > > > Well, I had meant the first 'cause it can be done with the existing byte > > code, but having the other one could be nice too. > > > > > > > > > -As a reply to "QT_Frame" I would like to get the passcount with the > > frame > > > > > > Hitcount, I assume you mean. Passcount is something different. > > > Yes, I'm sure we'd like that too. > > > > > > With all of these, however, we would have to talk about > > > the syntax for the remote protocol. We would not want > > > new syntax to break old existing stubs or debuggers. > > > > > > > and tracepoint numbers. > > > > > > Mmmmm... do we need that? The frame info ALWAYS contains > > > the PC, and the PC would generally uniquely identify a > > > tracepoint. > > > > > > > I guess I haven't thought enough about this one. How a different probed able > > command that will return list of tracepoints with their hitcounts? Would it > > be too noisy? > > You can do that now, I think. Well, you could, if you just > had the hitcounts. It's just a matter of processing the data > once you get it. You can either write gdb scripts or tcl/tk > code to produce whatever kind of report or display you want. Do you mean by walking through every frame? Wouldn't that be too clumsy? > > > > -In the future I will like to have a trace/ref of long address with > > > > base-offset parameters. > > > > > > Have to explain to me what you mean. > > > > Oh', it is just a special-trace-64-bits and special-trace-ref-64-bits > > commands for letting the target know it has to use bigger address. (in my > > case it means the target should pop two items from the stack instead of > > one). At the gdb side the user should be able to determine separately the > > base and the offset address. > > I don't understand -- is this another reference to your separate > address spaces? If the target architecture supports long pointers > and short pointers, then GDB should already know about that > (although I can't think of an architecture for which this is true.) > > I think you need to make this concept into something that can > be supported in the C expression language. Trace should > support anything that can be expressed as a C expression. > I withdraw this suggestion too (unless others are facing the need to capture 64 bits pointers (to another memory space) in 32 bits architecture) - Josef Ezra ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <m3d7grpa35.fsf@dan2.cygnus.com>]
[parent not found: <1001023235955.ZM13394@ocotillo.lan>]
* Re: That dwarf2read patch i just submitted [not found] ` <1001023235955.ZM13394@ocotillo.lan> @ 2000-10-24 11:34 ` Elena Zannoni 0 siblings, 0 replies; 4+ messages in thread From: Elena Zannoni @ 2000-10-24 11:34 UTC (permalink / raw) To: Kevin Buettner; +Cc: Daniel Berlin, gdb-patches The person has submitted a few other patches, always in that same time period (spring of 99). I haven't find an assignment from the FSF. Time to ask. Elena Kevin Buettner writes: > On Oct 23, 4:38pm, Daniel Berlin wrote: > > > Sigh. > > I'll redo the work then. > > Is there any way i can give him credit, without having to get a > > copyright assignment from him? > > In this case, you should first check to see if he has a copyright > assignment on file. If he does, there's no problem. > > If he doesn't, contact him and find out if he's willing to provide > one. This can be the hard part because, although he may be perfectly > willing, his employer might not be. (The employer also has to sign a > copyright disclaimer.) There's an added difficulty if he's changed > employer's since writing the patch. (A former employer may be even > more unwilling than normal to sign a copyright disclaimer for work > done by an ex-employee.) > > I know from first hand experience that it can be difficult to get the > employer to sign the copyright disclaimer. Some are perfectly > willing, but their legal departments decide to hold things up. > > Anyway... if you have trouble getting a disclaimer from either > the individual in question or their employer, I suppose that you > could try rewriting the patch yourself. But it is probably better > describe in English (without using code) what needs to be done > to this file and get someone else who hasn't seen the patch to > do it. I suppose you could then provide credit by saying something > like "Inspired by (but not based on) the work of ...". > > Or, if you had an obviously different implementation, that too > would likely suffice. > > If you do decide to reimplement Brian's patch, you should seek Andrew > Cagney's opinion first in order to make sure that your approach is > acceptable to the FSF. > > Kevin > From msnyder@cygnus.com Tue Oct 24 11:37:00 2000 From: Michael Snyder <msnyder@cygnus.com> To: gdb-patches@sourceware.cygnus.com Subject: [PATCH]: commands.exp -- clean up long lines and indentation Date: Tue, 24 Oct 2000 11:37:00 -0000 Message-id: <200010241837.LAA17209@cleaver.cygnus.com> X-SW-Source: 2000-10/msg00172.html Content-length: 26652 ... because I hate long lines and bad indentation. 2000-10-24 Michael Snyder <msnyder@cleaver.cygnus.com> * gdb.base/commands.exp: Break up long lines, and re-indent. Index: commands.exp =================================================================== RCS file: /cvs/src/src/gdb/testsuite/gdb.base/commands.exp,v retrieving revision 1.5 diff -c -3 -p -r1.5 commands.exp *** commands.exp 2000/06/07 04:14:02 1.5 --- commands.exp 2000/10/24 18:32:16 *************** proc gdbvar_simple_if_test {} { *** 45,53 **** gdb_test "set \$foo = 0" "" "set foo in gdbvar_simple_if_test" # All this test should do is print 0xdeadbeef once. ! gdb_test "if \$foo == 1\np/x 0xfeedface\nelse\np/x 0xdeadbeef\nend" "\\\$\[0-9\]* = 0xdeadbeef" "gdbvar_simple_if_test #1" # All this test should do is print 0xfeedface once. ! gdb_test "if \$foo == 0\np/x 0xfeedface\nelse\np/x 0xdeadbeef\nend" "\\\$\[0-9\]* = 0xfeedface" "gdbvar_simple_if_test #2" } proc gdbvar_simple_while_test {} { --- 45,55 ---- gdb_test "set \$foo = 0" "" "set foo in gdbvar_simple_if_test" # All this test should do is print 0xdeadbeef once. ! gdb_test "if \$foo == 1\np/x 0xfeedface\nelse\np/x 0xdeadbeef\nend" \ ! "\\\$\[0-9\]* = 0xdeadbeef" "gdbvar_simple_if_test #1" # All this test should do is print 0xfeedface once. ! gdb_test "if \$foo == 0\np/x 0xfeedface\nelse\np/x 0xdeadbeef\nend" \ ! "\\\$\[0-9\]* = 0xfeedface" "gdbvar_simple_if_test #2" } proc gdbvar_simple_while_test {} { *************** proc gdbvar_simple_while_test {} { *** 55,61 **** gdb_test "set \$foo = 5" "" "set foo in gdbvar_simple_while_test" # This test should print 0xfeedface five times. ! gdb_test "while \$foo > 0\np/x 0xfeedface\nset \$foo -= 1\nend" "\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface" "gdbvar_simple_while_test #1" } proc gdbvar_complex_if_while_test {} { --- 57,65 ---- gdb_test "set \$foo = 5" "" "set foo in gdbvar_simple_while_test" # This test should print 0xfeedface five times. ! gdb_test "while \$foo > 0\np/x 0xfeedface\nset \$foo -= 1\nend" \ ! "\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface" \ ! "gdbvar_simple_while_test #1" } proc gdbvar_complex_if_while_test {} { *************** proc gdbvar_complex_if_while_test {} { *** 63,69 **** gdb_test "set \$foo = 4" "" "set foo in gdbvar complex_if_while_test" # This test should alternate between 0xdeadbeef and 0xfeedface two times. ! gdb_test "while \$foo > 0\nset \$foo -= 1\nif \(\$foo % 2\) == 1\np/x 0xdeadbeef\nelse\np/x 0xfeedface\nend\nend" "\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface" "gdbvar_complex_if_while_test #1" } proc progvar_simple_if_test {} { --- 67,75 ---- gdb_test "set \$foo = 4" "" "set foo in gdbvar complex_if_while_test" # This test should alternate between 0xdeadbeef and 0xfeedface two times. ! gdb_test "while \$foo > 0\nset \$foo -= 1\nif \(\$foo % 2\) == 1\np/x 0xdeadbeef\nelse\np/x 0xfeedface\nend\nend" \ ! "\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface" \ ! "gdbvar_complex_if_while_test #1" } proc progvar_simple_if_test {} { *************** proc progvar_simple_if_test {} { *** 75,87 **** } if { ![runto factorial] } then { gdb_suppress_tests; } ! # Don't depend upon argument passing, since most simulators don't currently ! # support it. Bash value variable to be what we want. gdb_test "p value=5" "" "set value to 5 in progvar_simple_if_test #1" # All this test should do is print 0xdeadbeef once. ! gdb_test "if value == 1\np/x 0xfeedface\nelse\np/x 0xdeadbeef\nend" "\\\$\[0-9\]* = 0xdeadbeef" "progvar_simple_if_test #1" # All this test should do is print 0xfeedface once. ! gdb_test "if value == 5\np/x 0xfeedface\nelse\np/x 0xdeadbeef\nend" "\\\$\[0-9\]* = 0xfeedface" "progvar_simple_if_test #2" gdb_stop_suppressing_tests; } --- 81,97 ---- } if { ![runto factorial] } then { gdb_suppress_tests; } ! # Don't depend upon argument passing, since most simulators don't ! # currently support it. Bash value variable to be what we want. gdb_test "p value=5" "" "set value to 5 in progvar_simple_if_test #1" # All this test should do is print 0xdeadbeef once. ! gdb_test "if value == 1\np/x 0xfeedface\nelse\np/x 0xdeadbeef\nend" \ ! "\\\$\[0-9\]* = 0xdeadbeef" \ ! "progvar_simple_if_test #1" # All this test should do is print 0xfeedface once. ! gdb_test "if value == 5\np/x 0xfeedface\nelse\np/x 0xdeadbeef\nend" \ ! "\\\$\[0-9\]* = 0xfeedface" \ ! "progvar_simple_if_test #2" gdb_stop_suppressing_tests; } *************** proc progvar_simple_while_test {} { *** 95,105 **** gdb_test "set args 5" "" "set args in progvar_simple_while_test" if { ![runto factorial] } then { gdb_suppress_tests } ! # Don't depend upon argument passing, since most simulators don't currently ! # support it. Bash value variable to be what we want. gdb_test "p value=5" "" "set value to 5 in progvar_simple_if_test #2" # This test should print 0xfeedface five times. ! gdb_test "while value > 0\np/x 0xfeedface\nset value -= 1\nend" "\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface" "progvar_simple_while_test #1" gdb_stop_suppressing_tests; } --- 105,117 ---- gdb_test "set args 5" "" "set args in progvar_simple_while_test" if { ![runto factorial] } then { gdb_suppress_tests } ! # Don't depend upon argument passing, since most simulators don't ! # currently support it. Bash value variable to be what we want. gdb_test "p value=5" "" "set value to 5 in progvar_simple_if_test #2" # This test should print 0xfeedface five times. ! gdb_test "while value > 0\np/x 0xfeedface\nset value -= 1\nend" \ ! "\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface" \ ! "progvar_simple_while_test #1" gdb_stop_suppressing_tests; } *************** proc progvar_complex_if_while_test {} { *** 113,123 **** gdb_test "set args 4" "" "set args in progvar_complex_if_while_test" if { ![runto factorial] } then { gdb_suppress_tests } ! # Don't depend upon argument passing, since most simulators don't currently ! # support it. Bash value variable to be what we want. gdb_test "p value=4" "" "set value to 4 in progvar_simple_if_test" # This test should alternate between 0xdeadbeef and 0xfeedface two times. ! gdb_test "while value > 0\nset value -= 1\nif \(value % 2\) == 1\np/x 0xdeadbeef\nelse\np/x 0xfeedface\nend\nend" "\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface" "progvar_complex_if_while_test #1" gdb_stop_suppressing_tests; } --- 125,137 ---- gdb_test "set args 4" "" "set args in progvar_complex_if_while_test" if { ![runto factorial] } then { gdb_suppress_tests } ! # Don't depend upon argument passing, since most simulators don't ! # currently support it. Bash value variable to be what we want. gdb_test "p value=4" "" "set value to 4 in progvar_simple_if_test" # This test should alternate between 0xdeadbeef and 0xfeedface two times. ! gdb_test "while value > 0\nset value -= 1\nif \(value % 2\) == 1\np/x 0xdeadbeef\nelse\np/x 0xfeedface\nend\nend" \ ! "\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface" \ ! "progvar_complex_if_while_test #1" gdb_stop_suppressing_tests; } *************** proc if_while_breakpoint_command_test {} *** 129,136 **** gdb_test "set args 5" "" "set args in if_while_breakpoint_command_test" if { ![runto factorial] } then { gdb_suppress_tests } ! # Don't depend upon argument passing, since most simulators don't currently ! # support it. Bash value variable to be what we want. gdb_test "p value=5" "" "set value to 5 in progvar_simple_if_test" delete_breakpoints gdb_test "break factorial" "Breakpoint.*at.*" "break factorial #1" --- 143,150 ---- gdb_test "set args 5" "" "set args in if_while_breakpoint_command_test" if { ![runto factorial] } then { gdb_suppress_tests } ! # Don't depend upon argument passing, since most simulators don't ! # currently support it. Bash value variable to be what we want. gdb_test "p value=5" "" "set value to 5 in progvar_simple_if_test" delete_breakpoints gdb_test "break factorial" "Breakpoint.*at.*" "break factorial #1" *************** proc if_while_breakpoint_command_test {} *** 145,153 **** } } # This test should alternate between 0xdeadbeef and 0xfeedface two times. ! gdb_test "while value > 0\nset value -= 1\nif \(value % 2\) == 1\np/x 0xdeadbeef\nelse\np/x 0xfeedface\nend\nend\nend" "" "commands part 2 in if_while_breakpoint_command_test" ! gdb_test "continue" "\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface" "if_while_breakpoint_command_test #1" ! gdb_test "info break" "while.*set.*if.*p/x.*else.*p/x.*end.*" "info break in if_while_breakpoint_command_test" gdb_stop_suppressing_tests; } --- 159,173 ---- } } # This test should alternate between 0xdeadbeef and 0xfeedface two times. ! gdb_test "while value > 0\nset value -= 1\nif \(value % 2\) == 1\np/x 0xdeadbeef\nelse\np/x 0xfeedface\nend\nend\nend" \ ! "" \ ! "commands part 2 in if_while_breakpoint_command_test" ! gdb_test "continue" \ ! "\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface" \ ! "if_while_breakpoint_command_test #1" ! gdb_test "info break" \ ! "while.*set.*if.*p/x.*else.*p/x.*end.*" \ ! "info break in if_while_breakpoint_command_test" gdb_stop_suppressing_tests; } *************** proc infrun_breakpoint_command_test {} { *** 160,167 **** gdb_test "set args 6" "" "set args in progvar_simple_while_test" if { ![runto factorial] } then { gdb_suppress_tests } ! # Don't depend upon argument passing, since most simulators don't currently ! # support it. Bash value variable to be what we want. gdb_test "p value=6" "" "set value to 6 in progvar_simple_if_test #1" delete_breakpoints gdb_test "break factorial if value == 5" "Breakpoint.*at.*" --- 180,187 ---- gdb_test "set args 6" "" "set args in progvar_simple_while_test" if { ![runto factorial] } then { gdb_suppress_tests } ! # Don't depend upon argument passing, since most simulators don't ! # currently support it. Bash value variable to be what we want. gdb_test "p value=6" "" "set value to 6 in progvar_simple_if_test #1" delete_breakpoints gdb_test "break factorial if value == 5" "Breakpoint.*at.*" *************** proc infrun_breakpoint_command_test {} { *** 184,194 **** if { [istarget "hppa*-hp-hpux*"] } { gdb_test "continue" \ ! "Continuing.*.*.*Breakpoint \[0-9\]*, factorial \\(value=5\\).*at.*\[0-9\]*\[ \]*if \\(value > 1\\) \{.*\[0-9\]*\[ \]*value \\*= factorial \\(value - 1\\);.*" \ ! "continue in infrun_breakpoint_command_test" } else { gdb_test "continue" \ ! "Breakpoint \[0-9\]*, factorial \\(value=5\\).*at.* \[0-9\]*\[ \]*if \\(value > 1\\) \{.* \[0-9\]*\[ \]*value \\*= factorial \\(value - 1\\);.* factorial \\(value=4\\) at.*\[0-9\]*\[ \]*if \\(value > 1\\) \{.* --- 204,214 ---- if { [istarget "hppa*-hp-hpux*"] } { gdb_test "continue" \ ! "Continuing.*.*.*Breakpoint \[0-9\]*, factorial \\(value=5\\).*at.*\[0-9\]*\[ \]*if \\(value > 1\\) \{.*\[0-9\]*\[ \]*value \\*= factorial \\(value - 1\\);.*" \ ! "continue in infrun_breakpoint_command_test" } else { gdb_test "continue" \ ! "Breakpoint \[0-9\]*, factorial \\(value=5\\).*at.* \[0-9\]*\[ \]*if \\(value > 1\\) \{.* \[0-9\]*\[ \]*value \\*= factorial \\(value - 1\\);.* factorial \\(value=4\\) at.*\[0-9\]*\[ \]*if \\(value > 1\\) \{.* *************** factorial \\(value=3\\) at .* *** 200,206 **** #2 \[0-9a-fx\]* in factorial \\(value=5\\).* #3 \[0-9a-fx\]* in factorial \\(value=6\\).* #4 \[0-9a-fx\]* in main \\(.*\\).*" \ ! "continue in infrun_breakpoint_command_test"; } gdb_stop_suppressing_tests; --- 220,226 ---- #2 \[0-9a-fx\]* in factorial \\(value=5\\).* #3 \[0-9a-fx\]* in factorial \\(value=6\\).* #4 \[0-9a-fx\]* in main \\(.*\\).*" \ ! "continue in infrun_breakpoint_command_test"; } gdb_stop_suppressing_tests; *************** proc breakpoint_command_test {} { *** 214,227 **** gdb_test "set args 6" "" "set args in breakpoint_command_test" if { ![runto factorial] } then { gdb_suppress_tests; } ! # Don't depend upon argument passing, since most simulators don't currently ! # support it. Bash value variable to be what we want. gdb_test "p value=6" "" "set value to 6 in progvar_simple_if_test #2" delete_breakpoints gdb_test "break factorial" "Breakpoint.*at.*" "break factorial #2" gdb_test "commands\nprintf \"Now the value is %d\\n\", value\nend" \ "End with.*" "commands in breakpoint_command_test" ! gdb_test "continue" "Breakpoint \[0-9\]*, factorial.*Now the value is 5" \ "continue in breakpoint_command_test" gdb_test "print value" " = 5" "print value in breakpoint_command_test" gdb_stop_suppressing_tests; --- 234,248 ---- gdb_test "set args 6" "" "set args in breakpoint_command_test" if { ![runto factorial] } then { gdb_suppress_tests; } ! # Don't depend upon argument passing, since most simulators don't ! # currently support it. Bash value variable to be what we want. gdb_test "p value=6" "" "set value to 6 in progvar_simple_if_test #2" delete_breakpoints gdb_test "break factorial" "Breakpoint.*at.*" "break factorial #2" gdb_test "commands\nprintf \"Now the value is %d\\n\", value\nend" \ "End with.*" "commands in breakpoint_command_test" ! gdb_test "continue" \ ! "Breakpoint \[0-9\]*, factorial.*Now the value is 5" \ "continue in breakpoint_command_test" gdb_test "print value" " = 5" "print value in breakpoint_command_test" gdb_stop_suppressing_tests; *************** proc user_defined_command_test {} { *** 243,252 **** } } # This test should alternate between 0xdeadbeef and 0xfeedface two times. ! gdb_test "while \$arg0 > 0\nset \$arg0 -= 1\nif \(\$arg0 % 2\) == 1\np/x 0xdeadbeef\nelse\np/x 0xfeedface\nend\nend\nend" "" "enter commands in user_defined_command_test" ! ! gdb_test "mycommand \$foo" "\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface" "execute user defined command in user_defined_command_test" ! gdb_test "show user mycommand" "while.*set.*if.*p/x.*else.*p/x.*end.*" "display user command in user_defined_command_test" } proc watchpoint_command_test {} { --- 264,279 ---- } } # This test should alternate between 0xdeadbeef and 0xfeedface two times. ! gdb_test "while \$arg0 > 0\nset \$arg0 -= 1\nif \(\$arg0 % 2\) == 1\np/x 0xdeadbeef\nelse\np/x 0xfeedface\nend\nend\nend" \ ! "" \ ! "enter commands in user_defined_command_test" ! ! gdb_test "mycommand \$foo" \ ! "\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface\[^\n\]*\n\\\$\[0-9\]* = 0xdeadbeef\[^\n\]*\n\\\$\[0-9\]* = 0xfeedface" \ ! "execute user defined command in user_defined_command_test" ! gdb_test "show user mycommand" \ ! "while.*set.*if.*p/x.*else.*p/x.*end.*" \ ! "display user command in user_defined_command_test" } proc watchpoint_command_test {} { *************** proc watchpoint_command_test {} { *** 290,330 **** send_gdb "commands $wp_id\n" gdb_expect { ! -re "Type commands for when breakpoint $wp_id is hit, one per line.*>"\ ! {pass "begin commands on watch"} ! -re "$gdb_prompt $"\ ! {fail "begin commands on watch"} ! timeout {fail "(timeout) begin commands on watch"} } send_gdb "print value\n" gdb_expect { ! -re ">"\ ! {pass "add print command to watch"} ! -re "$gdb_prompt $"\ ! {fail "add print command to watch"} ! timeout {fail "(timeout) add print command to watch"} } send_gdb "continue\n" gdb_expect { ! -re ">"\ ! {pass "add continue command to watch"} ! -re "$gdb_prompt $"\ ! {fail "add continue command to watch"} ! timeout {fail "(timeout) add continue command to watch"} } send_gdb "end\n" gdb_expect { ! -re "$gdb_prompt $"\ ! {pass "begin commands on watch"} ! timeout {fail "(timeout) begin commands on watch"} } send_gdb "continue\n" gdb_expect { ! -re "Continuing.*\[Ww\]atchpoint $wp_id deleted because the program has left the block in.*which its expression is valid.*run.c:57.*$gdb_prompt $"\ ! {pass "continue with watch"} ! -re "$gdb_prompt $"\ ! {fail "continue with watch"} ! timeout {fail "(timeout) continue with watch"} } } --- 317,352 ---- send_gdb "commands $wp_id\n" gdb_expect { ! -re "Type commands for when breakpoint $wp_id is hit, one per line.*>" { ! pass "begin commands on watch" ! } ! -re "$gdb_prompt $" {fail "begin commands on watch"} ! timeout {fail "(timeout) begin commands on watch"} } send_gdb "print value\n" gdb_expect { ! -re ">" {pass "add print command to watch"} ! -re "$gdb_prompt $" {fail "add print command to watch"} ! timeout {fail "(timeout) add print command to watch"} } send_gdb "continue\n" gdb_expect { ! -re ">" {pass "add continue command to watch"} ! -re "$gdb_prompt $" {fail "add continue command to watch"} ! timeout {fail "(timeout) add continue command to watch"} } send_gdb "end\n" gdb_expect { ! -re "$gdb_prompt $" {pass "begin commands on watch"} ! timeout {fail "(timeout) begin commands on watch"} } send_gdb "continue\n" gdb_expect { ! -re "Continuing.*\[Ww\]atchpoint $wp_id deleted because the program has left the block in.*which its expression is valid.*run.c:57.*$gdb_prompt $" { ! pass "continue with watch" ! } ! -re "$gdb_prompt $" {fail "continue with watch"} ! timeout {fail "(timeout) continue with watch"} } } *************** proc test_command_prompt_position {} { *** 337,375 **** } if { ![runto factorial] } then { gdb_suppress_tests; } ! # Don't depend upon argument passing, since most simulators don't currently ! # support it. Bash value variable to be what we want. delete_breakpoints gdb_test "break factorial" "Breakpoint.*at.*" "break factorial #2" gdb_test "p value=5" "" "set value to 5 in test_command_prompt_position" # All this test should do is print 0xdeadbeef once. ! gdb_test "if value == 1\np/x 0xfeedface\nelse\np/x 0xdeadbeef\nend" "\\\$\[0-9\]* = 0xdeadbeef" "if test in test_command_prompt_position" ! ! # Now let's test for the correct position of the '>' in gdb's prompt for commands. ! # It should be at the beginning of the line, and not after one space. send_gdb "commands\n" gdb_expect { ! -re "Type commands.*End with.*\[\r\n\]>$" \ ! { send_gdb "printf \"Now the value is %d\\n\", value\n" ! gdb_expect { ! -re "^printf.*value\r\n>$" \ ! { send_gdb "end\n" ! gdb_expect { ! -re "^end\r\n$gdb_prompt $" { pass "> OK in test_command_prompt_position" } ! -re ".*$gdb_prompt $" { fail "some other message in test_command_prompt_position" } ! timeout { fail "(timeout) 1 in test_command_prompt_position" } ! } ! } ! -re "^ >$" { fail "> not OK in test_command_prompt_position" } ! -re ".*$gdb_prompt $" { fail "wrong message in test_command_prompt_position" } ! timeout { fail "(timeout) 2 in test_command_prompt_position " } ! } ! } ! -re "Type commands.*End with.*\[\r\n\] >$" { fail "prompt not OK in test_command_prompt_position" } ! -re ".*$gdb_prompt $" { fail "commands in test_command_prompt_position" } ! timeout { fail "(timeout) 3 commands in test_command_prompt_position" } } gdb_stop_suppressing_tests; } --- 359,414 ---- } if { ![runto factorial] } then { gdb_suppress_tests; } ! # Don't depend upon argument passing, since most simulators don't ! # currently support it. Bash value variable to be what we want. delete_breakpoints gdb_test "break factorial" "Breakpoint.*at.*" "break factorial #2" gdb_test "p value=5" "" "set value to 5 in test_command_prompt_position" # All this test should do is print 0xdeadbeef once. ! gdb_test "if value == 1\np/x 0xfeedface\nelse\np/x 0xdeadbeef\nend" \ ! "\\\$\[0-9\]* = 0xdeadbeef" \ ! "if test in test_command_prompt_position" ! ! # Now let's test for the correct position of the '>' in gdb's ! # prompt for commands. It should be at the beginning of the line, ! # and not after one space. send_gdb "commands\n" gdb_expect { ! -re "Type commands.*End with.*\[\r\n\]>$" { ! send_gdb "printf \"Now the value is %d\\n\", value\n" ! gdb_expect { ! -re "^printf.*value\r\n>$" { ! send_gdb "end\n" ! gdb_expect { ! -re "^end\r\n$gdb_prompt $" { ! pass "> OK in test_command_prompt_position" ! } ! -re ".*$gdb_prompt $" { ! fail "some other message in test_command_prompt_position" ! } ! timeout { ! fail "(timeout) 1 in test_command_prompt_position" ! } ! } ! } ! -re "^ >$" { fail "> not OK in test_command_prompt_position" } ! -re ".*$gdb_prompt $" { ! fail "wrong message in test_command_prompt_position" ! } ! timeout { ! fail "(timeout) 2 in test_command_prompt_position " ! } ! } ! } ! -re "Type commands.*End with.*\[\r\n\] >$" { ! fail "prompt not OK in test_command_prompt_position" ! } ! -re ".*$gdb_prompt $" { ! fail "commands in test_command_prompt_position" } + timeout { fail "(timeout) 3 commands in test_command_prompt_position" } + } gdb_stop_suppressing_tests; } *************** proc test_command_prompt_position {} { *** 377,403 **** proc deprecated_command_test {} { - - gdb_test "maintenance deprecate blah" "Can't find command.*" \ "tried to deprecate non-existsing command" gdb_test "maintenance deprecate p \"new_p\"" "" ! gdb_test "p 5" "Warning: 'p', an alias for the command 'print' is deprecated.*Use 'new_p'.*" "p deprecated warning, with replacement" gdb_test "p 5" ".\[0-9\]* = 5.*" "Deprecated warning goes away" gdb_test "maintenance deprecate p \"new_p\"" "" gdb_test "maintenance deprecate print \"new_print\"" "" ! gdb_test "p 5" "Warning: command 'print' \\(p\\) is deprecated.*Use 'new_print'.*" "both alias and command are deprecated" gdb_test "p 5" ".\[0-9\]* = 5.*" "Deprecated warning goes away" - - gdb_test "maintenance deprecate set remote memory-read-packet-size \"srm\" " "" "deprecate long comamnd" - gdb_test "set remote memory-read-packet-size" "Warning: command 'set remote memory-read-packet-size' is deprecated.*Use 'srm'.*" "long command deprecated" - - gdb_test "maintenance deprecate set remote memory-read-packet-size" "" "deprecate long comamnd" - gdb_test "set remote memory-read-packet-size" "Warning: command 'set remote memory-read-packet-size' is deprecated.*No alternative known.*" "long command deprecated with no alternative." ! gdb_test "maintenance deprecate" "\"maintenance deprecate\".*" "deprecate with no arguments" } --- 416,454 ---- proc deprecated_command_test {} { gdb_test "maintenance deprecate blah" "Can't find command.*" \ "tried to deprecate non-existsing command" gdb_test "maintenance deprecate p \"new_p\"" "" ! gdb_test "p 5" \ ! "Warning: 'p', an alias for the command 'print' is deprecated.*Use 'new_p'.*" \ ! "p deprecated warning, with replacement" gdb_test "p 5" ".\[0-9\]* = 5.*" "Deprecated warning goes away" gdb_test "maintenance deprecate p \"new_p\"" "" gdb_test "maintenance deprecate print \"new_print\"" "" ! gdb_test "p 5" \ ! "Warning: command 'print' \\(p\\) is deprecated.*Use 'new_print'.*" \ ! "both alias and command are deprecated" gdb_test "p 5" ".\[0-9\]* = 5.*" "Deprecated warning goes away" ! gdb_test "maintenance deprecate set remote memory-read-packet-size \"srm\" " \ ! "" \ ! "deprecate long comamnd" ! gdb_test "set remote memory-read-packet-size" \ ! "Warning: command 'set remote memory-read-packet-size' is deprecated.*Use 'srm'.*" \ ! "long command deprecated" ! ! gdb_test "maintenance deprecate set remote memory-read-packet-size" \ ! "" \ ! "deprecate long comamnd" ! gdb_test "set remote memory-read-packet-size" \ ! "Warning: command 'set remote memory-read-packet-size' is deprecated.*No alternative known.*" \ ! "long command deprecated with no alternative." ! ! gdb_test "maintenance deprecate" \ ! "\"maintenance deprecate\".*" \ ! "deprecate with no arguments" } From ezannoni@cygnus.com Tue Oct 24 11:46:00 2000 From: Elena Zannoni <ezannoni@cygnus.com> To: Daniel Berlin <dberlin@redhat.com> Cc: Kevin Buettner <kevinb@cygnus.com>, gdb-patches@sources.redhat.com Subject: Re: That dwarf2read patch i just submitted Date: Tue, 24 Oct 2000 11:46:00 -0000 Message-id: <14837.55523.942503.523490@kwikemart.cygnus.com> References: <m3zojvmz9j.fsf@dan2.cygnus.com> <1001023165317.ZM12542@ocotillo.lan> <m3aebvqyxy.fsf@dan2.cygnus.com> <1001023173236.ZM12624@ocotillo.lan> <m3d7grpa35.fsf@dan2.cygnus.com> <1001023235955.ZM13394@ocotillo.lan> <14837.54804.638957.639280@kwikemart.cygnus.com> X-SW-Source: 2000-10/msg00173.html Content-length: 338 Elena Zannoni writes: > > > The person has submitted a few other patches, always in that same > time period (spring of 99). I haven't find an assignment from the FSF. > > Time to ask. > > Elena > A mail to him bounced. I am afraid we must think of plan B. Unless we can get in touch with somebody at the company. Elena ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <39F60D7B.C901357F@apple.com>]
[parent not found: <39F6D4BB.8431FC3C@cygnus.com>]
* Re: That dwarf2read patch i just submitted [not found] ` <39F6D4BB.8431FC3C@cygnus.com> @ 2000-10-25 7:19 ` Daniel Berlin 0 siblings, 0 replies; 4+ messages in thread From: Daniel Berlin @ 2000-10-25 7:19 UTC (permalink / raw) To: Andrew Cagney; +Cc: Stan Shebs, Kevin Buettner, gdb-patches Andrew Cagney <ac131313@cygnus.com> writes: > > > Andrew > (who doesn't know any lawyers) Here's a frightening thought: In 3 years, i'll be a lawyer. --Dan ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2000-10-25 7:19 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-10-23 7:02 That dwarf2read patch i just submitted Daniel Berlin
[not found] ` <1001023165317.ZM12542@ocotillo.lan>
[not found] ` <m3aebvqyxy.fsf@dan2.cygnus.com>
2000-10-23 10:32 ` Kevin Buettner
[not found] ` <m3d7grpa35.fsf@dan2.cygnus.com>
[not found] ` <1001023235955.ZM13394@ocotillo.lan>
2000-10-24 11:34 ` Elena Zannoni
[not found] ` <39F60D7B.C901357F@apple.com>
[not found] ` <39F6D4BB.8431FC3C@cygnus.com>
2000-10-25 7:19 ` Daniel Berlin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox