Re: random debugging, What should I prepare for a PL PhD program

Hans-Peter Diettrich <DrDiettrich1@netscape.net>
Sun, 23 Oct 2022 01:27:18 +0200

          From comp.compilers
Related articles
What should I prepare for a PL PhD program tianboh@alumni.cmu.edu (Tianbo Hao) (2022-10-18)
RE: What should I prepare for a PL PhD program nuno.lopes@tecnico.ulisboa.pt (Nuno Lopes) (2022-10-19)
Re: What should I prepare for a PL PhD program DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2022-10-20)
Re: What should I prepare for a PL PhD program spibou@gmail.com (Spiros Bousbouras) (2022-10-21)
Re: What should I prepare for a PL PhD program tkoenig@netcologne.de (Thomas Koenig) (2022-10-21)
Re: random debugging, What should I prepare for a PL PhD program gah4@u.washington.edu (gah4) (2022-10-21)
Re: random debugging, What should I prepare for a PL PhD program tkoenig@netcologne.de (Thomas Koenig) (2022-10-22)
Re: random debugging, What should I prepare for a PL PhD program DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2022-10-23)
Re: random debugging, What should I prepare for a PL PhD program gah4@u.washington.edu (gah4) (2022-10-23)
Re: random debugging, What should I prepare for a PL PhD program tkoenig@netcologne.de (Thomas Koenig) (2022-10-23)
| List of all articles for this month |
From: Hans-Peter Diettrich <DrDiettrich1@netscape.net>
Newsgroups: comp.compilers
Date: Sun, 23 Oct 2022 01:27:18 +0200
Organization: Compilers Central
References: 22-10-029 22-10-031 22-10-035 22-10-036 22-10-039 22-10-040 22-10-042
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="87767"; mail-complaints-to="abuse@iecc.com"
Keywords: debug
Posted-Date: 22 Oct 2022 22:51:42 EDT
In-Reply-To: 22-10-042

On 10/22/22 10:49 AM, Thomas Koenig wrote:


> An automated code generator which generates valid programs according
> to the syntax and semantics rules of a langauge and then systematically
> violates the rules (especially those prescribed outside the formal
> grammar) one by one might be possible. Alternatively, it might
> also be feasible to parse an existing code base and systematically
> insert violations there.


Isn't it good practice to maintain a test suite at least for compilers,
that contains both selected valid and invalid code snippets?


For error reports on obviously weird input I'd prepare an equally weird
answer ;-)


DoDi

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.